Decimal formatter issue

Hi All,
In a datagrid I use labelFunction method to format input numbers, this function will format decimal numbers with precision 2.
public static function formatDecimal(val:Number):String
            var decimalFormatter: NumberFormatter = new NumberFormatter();
            decimalFormatter.rounding = "up";
            decimalFormatter.precision = 2;
            decimalFormatter.useNegativeSign = false;
            return decimalFormatter.format(val);
Now, if the input is 2.55 only, it format the number to 2.56. It is a way to prevent this?
It should format 2.56 if the input is 2.555. correct?
Thanks
JFB

This is strange, it happens only with 8.55, it converts to 8.56 but my total calculations on the grid is reading 8.55 not 8.56.
Is not doing the same for 2.55, 3.55 or 4.55
Any ideas? Is this a bug?
Thanks!
JFB

Similar Messages

EA1 - SQL Formatter issues (JOINs and GROUPs and ORDER BY oh my ;)

Great job with improving the SQL Formatter, but it still has some bugs that need to be worked out.
The key words JOIN and it's modifiers INNER, LEFT, RIGHT and FULL OUTER are not recognized as master key words. As such they end up flush against the left margin Also when GROUP BY and/or ORDER BY key words are present in an outer most select statement the other key words are not indented far enough to be right aligned with the end of the word BY and are indented too far to be right aligned with the word GROUP or ORDER. In sub queries, GROUP and ORDER BY are correctly right aligned with their respective SELECT statements.

We're picking up and collating the Formatter issues. I'll add these.
Specific bug for these #7013462
Sue

Production order Unit of Messure-decimal rounding issue

Finished product is a Metal conveyor belt.
Material Base UoM is Links u2018LKu2019
Alternative UoM are:
10 link = 1 Feet
1 meter = 3.2808 Feet
Plant X800, (MTO) Sales orders created in meters. So production orders in Meters (MM02->work scheduling view->Production unit & Unit of Issue maintained in Meters)
Now Issue is:
If production order is 10 meters, this is converted to 328.084 LK. Physically shopfloor receives only 328 LKs after production.
Links cannot be in decimals. Inventory and Costing is done u2018per Linku2019.
This needs a decimal rounding to u20180u2019 value. Expectation will be 328 LK.
If the value is 1.49 then the rounding value will be u20181u2019 (< 0.5)
If the value is 1.5 then the rounding value will be u20182u2019 (>0.5)
Please help me. Is there a config Setting or a work around (user exit)?

Your requirement cannot be fulfilled by customization. Nor it can be perfectly implemented though BAdI's or Userexits.
The settings in CUNI only hide the decimal zeros but it won't prevent either users or programs to enter decimals. in R/3 quantity field uses the domain MENG13 so in your case, in the production order it will always display in decimals (eg 328.084 LK) .You can refer to note for more understanding about CUNI settings and IM postings 931971
Also the following threads:
UOM EA is taking data in decimals
The solution (this is more of workaround) I would suggest is you need to implement a BAdI WORKORDER_GOODSMVT in which it will round off according the logic you mentioned in your posts above. Also you need to implement a user exit for CO11N/CO11/15 to confirm the same yield according to the same rounding logic. Since yours is MTO you need to evaluate the impact of this in other areas mainly controlling and finance.

Asian (JPY) currency Decimal Places Issue

HI All,
Need your help, we have a program which creates a BDC session and when the user tries to process it it throws an errror for amount in asian currencies like JPY - no decimal places allowed for currency, in the background it calls the FBB1 transaction.
The original amount is in USD however after conversion when we store it back to amount field which is of type
"glpct-tslvt" it stores the amount in JPY currency with decimal places so for example :
USD amount = 93,214. 00
JPY amount = 115,021. 86
guess the amount is stored with decimals in BSEG table, so now when we try to process the session with the JPY amount with decimals it throws an error.
I have tried the
CALL FUNCTION 'CURRENCY_AMOUNT_SAP_TO_DISPLAY'
and
CALL FUNCTION 'BAPI_CURRENCY_GETDECIMALS'
it gives me the correct value for amount so for above example JPY amount = 115,021. 86 by using the mentioned two methods i am able to get the currency in this format 11502186.00 but still has two decimal places, i think it still will not work when we process the session for FBB1.
Need your help people, appreciate your co-operation.

sorry to revive an old thread...but we are having an issue with JPY in our electronic bank statements.
the BAI format for our JPY account has for example 900 yen which according to our finance department is really 9 yen. the bank claims this is a known issue and the BAI format documentation seems to be confirming the bank's position in that the decimals are implied according to the currency code (whatever that means in SAP terms is a bit foggy to us).....
currently we wrote a custom code to suppress the last two zeros (when they are zeros) but i feel this error is caused either by a wrong setting in our currency or translation tables in SAP or something else since our feeling is that this should work right out of the box without any custom programming...any ideas???...where we shoudl start looking in our currency config....does the 100:1 or 1:1 translation ratio between JPY/USD make any difference...should we try and use a function module to convert the currency ...any ideas or hints are welcome
thanks
Ram
[email protected]

LabVIEW to Excel - decimal separator issue

I'm using a VI to copy a LabVIEW table to Excel
http://forums.ni.com/ni/attachments/ni/170/125802/1/Write_Table_and_Chart_to_XL.llb
My system uses the comma as a standard decimal separator. Despite changing the LabVIEW settings the table I generate uses a decimal point. When I copy the data values smaller than one are copied correctly, but values > 1 are recognized as the value times a million.
0,9 is still 0,9 but 1,34 is 1340000
Is there any way to resolve this issue
Thanks
Solved!
Go to Solution.

I ran your VI and everything looks fine for me!!
I get the attached table when I ran the code.
Are you using any non-english keybord? or is there any default settings in Excel with formatted cells?
Iam using LV8.5, and I changed the range property's value to Value2 in Set Cell Value.vi (since it had a broken arrow)
Message Edited by Vsh on 11-09-2009 02:55 AM
Attachments:
result.xls ‏14 KB

Formatter issue

I have a strange issue at hand. I am trying to apply a formatter to format date to one of the fields but the formatter function never gets invoked.
I tried with XMl and JS views but non of them seems to work is there any trick I am missing.
I am also using lazy loading because I thought eager loding of views might be issue but no use.
Here is code in contention
var oTemplate = new sap.m.ColumnListItem({
type:"Navigation",
press:oController.handleProjectSelected,
cells:[
        new sap.m.ObjectIdentifier({title:"{displayName}"}),
        new sap.m.Text({
        path:"creationDate",
        formatter:"util.Formatter.date"
        new sap.m.Label({
        text:"{creatorUserName}"
        new sap.m.Text({
        path:"lastDataUpdateDate",
        formatter:"util.Formatter.date"
//Same for XML view
<ColumnListItem
type="Navigation"
press="handleProjectSelected">
<cells>
<ObjectIdentifier title="{displayName}"/>
<Text text="{
path:'creationDate',
formatter:'util.Formatter.date'
}"/>
<Text text="{creatorUserName}"/>
<Text text="{
path:'lastDataUpdateDate',
formatter:'util.Formatter.date'
}"/>
</cells>
<customData>
<core:CustomData
key="target"
value="Project"/>
</customData>
</ColumnListItem>
Here is Formatter code it never gets invoked
jQuery.sap.declare("util.Formatter");
jQuery.sap.require("sap.ui.core.format.DateFormat");
util.Formatter = {
date : function (value) {
if (value) {
var oDateFormat = sap.ui.core.format.DateFormat.getDateTimeInstance({pattern: "yyyy-MM-dd"});
return oDateFormat.format(new Date(value));
} else {
return value;

Hi,
Since you can specify a formatter for basically any attribute, you should also specify for which attribute you want tho use a formatter.
For instance, the following code uses a formatter for both 'text' and 'valueState' properties:
var oTV = new sap.ui.commons.TextView({
    text: {
        parts: ["mydatefield"],
        formatter: function(oValue) {
            if (oValue != undefined) {
                var yyyy = oValue.getFullYear().toString();
                var mm = (oValue.getMonth() + 1).toString(); // getMonth() is zero-based
                var dd = oValue.getDate().toString();
                return yyyy + '/' + (mm[1] ? mm : "0" + mm[0]) + '/' + (dd[1] ? dd : "0" + dd[0]);
            } else return "";
    valueState: {
        parts: ["mydatefield"],
        formatter: function(oValue) {
            return (oValue === undefined || oValue == null) ? sap.ui.core.ValueState.Error : sap.ui.core.ValueState.None;
Hope this explains!
R.

Condition type decimal point issue in pricing

Hi
I have a import pricing Procedure as shown
The condition types JEDB and JSED were calculated on 0.16 EUR,
Like JEDB 2% of 0.16EUR= 0.0032
and JSED 1% of 0.16EUR= 0.0016
it is taking the first two digits of the value, ie 0.00 only
Please confirm how to come with the corrected values,
Thanks,

Yes it is intended for TM but you can do the manual changes as recommended in the note and for technical coding, you can copy that logic. Else, have a look at this note:-
Note 38881 - Pricing with different decimal places
G. Lakshmipathi

BIG DECIMAL DATATYPE ISSUE IN JDEV 10.1.3.2 ADF BC

I am developing a small application on mysql db. in one of my entry screens i have to input numeric data upto a 4 decimal places.
My project settings are SQL92 and JAVA types.
My dataype for the numeric field in db is double(17,4) at entity level i have kept it to bigdecimal.
When i enter something as 1200.1223 and save it . it saves correctly but when i modify the same record i get 1200.1222222292222291 value in my input box.
can any body help what i am doing wrong?
regards
Amit

Pravin
We dont get number datatype if you have SQL92 selected as SQL Flavour. So i dont think this would help. SQL TYPE Map is JAVA basically in my project. Do you want me to import some of oracle.jbo.domains specifically or something else you want me to do
regards
Amit

How to resolve the decimal point issue??

hello friends,
I had declared a variable of variable type P(16) decimals 6 for price. The price is calculated accurately and stored in the variable. The value that got stored is 5094390.000000. I declared one more variable of type ekpo-netpr and moved that value into this field. In the fieldcatalog i used cfieldname = 'waers'.....while displaying through ALV for waers 'IDR' (no decimals should be displayed ) it is displaying as 509.439.000 instead of 5094390.
Could you tell me any one dd variable that can hold of type P(16) decimals 6 .
pls help me to resolve this issue. All helpful answers would be highly rewarded.
Thanks,
Ramineni

Hi Ramineni,
Check this..
WA_FCAT-TABNAME = 'I_OUTTAB'.
WA_FCAT-FIELDNAME = 'AUFNR'.
WA_FCAT-REF_TABNAME = 'AUFK'.
WA_FCAT-HOTSPOT = 'X'.
APPEND WA_FCAT TO I_FCAT.
WA_FCAT-TABNAME = 'I_OUTTAB'.
WA_FCAT-FIELDNAME = 'ACTL'.
WA_FCAT-SELTEXT_M = 'Total Act Amount'(010).
WA_FCAT-QFIELDNAME = 'TWAER'.
WA_FCAT-QTABNAME = 'T_OUTTAB'.
wa_fcat-decimals_o = '0'.
APPEND WA_FCAT TO I_FCAT.
CLEAR WA_FCAT.
<b>Decimals in this will be restricted</b>
Regards,
Omkar.

Crystal reports decimal separator issue

Post Author: Ramco
CA Forum: General
In crystal reports XI and crystal reports XI R2 decimal separator is not changing according to regional setting. In report designer we have formated the field display style to "System Default Number format" and changed the regional settings to German(123.345.678,90).Still it is displaying the English(United States) format (123,345,678.90).Note: It is working fine in standalone applications.Problem is only with the web based appications.

Post Author: royaouad
CA Forum: General
hi Ramco
i have the same problem as u have. did u find any solution. if yes could u please tell me?

EA1: A few formatter issues

1. Alignment of AND keywords in select statement is wrong.
function get_segment_size(ownname in varchar2,   segname in varchar2, segtype in varchar2) return number is indsize number(16);
begin
    begin
      select bytes
      into indsize
      from dba_segments
      where owner = ownname
       and segment_type = segtype
       and segment_name = segname;
    exception
    when others then
      raise;
    end;
    return indsize;
end;becomes
FUNCTION get_segment_size
    ownname IN VARCHAR2,
    segname IN VARCHAR2,
    segtype IN VARCHAR2 )
RETURN NUMBER
IS
indsize NUMBER ( 16 ) ;
BEGIN
BEGIN
     SELECT bytes
       INTO indsize
       FROM dba_segments
      WHERE owner = ownname
AND segment_type = segtype
AND segment_name = segname;
EXCEPTION
WHEN OTHERS THEN
    raise;
END;
RETURN indsize;
END;The ANDs are left aligned with the enclosing block rather than right aligned with the 'master keywords'.
2. NUMBER(?,?) and VARCHAR2(?) declarations have parentheses and sizes split over multiple lines.
index_list dba_indexes_tab;
rebuild_stmt varchar2(200);
end_time date;
start_size number(16,   0);
end_size number(16,   0);
batch app_support_batch_runs % rowtype;
batch_results resultset;becomes
index_list dba_indexes_tab;
rebuild_stmt VARCHAR2
    200
end_time DATE;
start_size NUMBER
    16, 0
end_size NUMBER
    16, 0
batch app_support_batch_runs % rowtype;
batch_results resultset;3. Some array subscripted expressions have their parentheses split across multiple lines.
    end_time := sysdate;
    batch_results := resultset();
    batch_results.extend;
    batch_results(batch_results.last).asjr_result_type := 'ELAPSED_TIME';
    batch_results(batch_results.last).asjr_result_key := 'ALL';
    batch_results(batch_results.last).asjr_result_value :=((end_time -batch.asbr_component_start_time) *(24 *60 *60));becomes
end_time      := sysdate;
batch_results := resultset
batch_results.extend;
batch_results
    batch_results.last
.asjr_result_type := 'ELAPSED_TIME';
batch_results
    batch_results.last
.asjr_result_key := 'ALL';
batch_results
    batch_results.last
.asjr_result_value :=
    ( end_time -batch.asbr_component_start_time ) * ( 24 *60 *60 )
;Another similar block later in the same package is left as single lines.
4. 3 seems to apply generally to expressions involving parentheses - array subscripts, procedure calls. Some are done properly, others are spread across multiple lines.
5. Various keywords are not recognised by the formatter, although they are by the syntax highlighter. (They are in bold, but not upper case)
raise
extend
last
immediate
6. There doesn't seem to be away to format the current selection rather than the whole buffer (in the PL/SQL editor)

Given this -
select prej.asbr_component_name,
prej.asbr_batch_start_time,
etime.asjr_result_value Elapsed,
prer.asjr_result_value Size_before,
postr.asjr_result_value Size_after,
prer.asjr_result_value -postr.asjr_result_value Shrinkage
from app_support_batch_runs prej
inner join app_support_job_result prer on prer.asjr_asbr_id = prej.asbr_id
inner join app_support_job_result postr on postr.asjr_asbr_id = prej.asbr_id
inner join app_support_job_result etime on etime.asjr_asbr_id = prej.asbr_id
where prer.asjr_result_type = 'START_SIZE'
and postr.asjr_result_type = 'END_SIZE'
and etime.asjr_result_type = 'ELAPSED_TIME'
order by prej.asbr_component_name;with [em]indent AND/OR[em] unchecked, you get this.
SELECT prej.asbr_component_name    ,
prej.asbr_batch_start_time        ,
etime.asjr_result_value Elapsed   ,
prer.asjr_result_value Size_before,
postr.asjr_result_value Size_after,
prer.asjr_result_value -postr.asjr_result_value Shrinkage
   FROM app_support_batch_runs prej
INNER JOIN app_support_job_result prer
     ON prer.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result postr
     ON postr.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result etime
     ON etime.asjr_asbr_id    = prej.asbr_id
WHERE prer.asjr_result_type = 'START_SIZE'
AND postr.asjr_result_type    = 'END_SIZE'
AND etime.asjr_result_type    = 'ELAPSED_TIME'
ORDER BY prej.asbr_component_name;The problems with this are.
1) The sql statement as a whole is indented (ie the select keyword)
2) Despite 1), INNER, AND and ORDER are NOT indented at all whereas the should be at least level with the select. I suspect the problem may be that it is trying to right align 'INNER JOIN' and 'ORDER BY' with the SELECT-FROM-WHERE.I thing the ON of the join clauses is right aligned.
3) The column list isn't right. The columns should be left aligned and positioned one space to the right of the select keyword ( or at a pinch on a new line, indented from the select keyword by 2 columns)
with [em]indent AND/OR[em] checked, you get this.
SELECT prej.asbr_component_name    ,
prej.asbr_batch_start_time        ,
etime.asjr_result_value Elapsed   ,
prer.asjr_result_value Size_before,
postr.asjr_result_value Size_after,
prer.asjr_result_value -postr.asjr_result_value Shrinkage
   FROM app_support_batch_runs prej
INNER JOIN app_support_job_result prer
     ON prer.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result postr
     ON postr.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result etime
     ON etime.asjr_asbr_id    = prej.asbr_id
WHERE prer.asjr_result_type = 'START_SIZE'
AND postr.asjr_result_type = 'END_SIZE'
AND etime.asjr_result_type = 'ELAPSED_TIME'
ORDER BY prej.asbr_component_name;This is better but still has the problems with right-alignment.
With [em]Right-align master keywords[em] unchecked...
SELECT prej.asbr_component_name     ,
prej.asbr_batch_start_time        ,
etime.asjr_result_value Elapsed   ,
prer.asjr_result_value Size_before,
postr.asjr_result_value Size_after,
prer.asjr_result_value -postr.asjr_result_value Shrinkage
FROM app_support_batch_runs prej
INNER JOIN app_support_job_result prer
ON prer.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result postr
ON postr.asjr_asbr_id = prej.asbr_id
INNER JOIN app_support_job_result etime
ON etime.asjr_asbr_id        = prej.asbr_id
WHERE prer.asjr_result_type = 'START_SIZE'
AND postr.asjr_result_type = 'END_SIZE'
AND etime.asjr_result_type = 'ELAPSED_TIME'
ORDER BY prej.asbr_component_name;IMO This is best but I would like ON indented with respect to the INNER JOIN it belongs to.
So in terms of this sql statement, I think the only bug is the alignment of columns. The right alignment option doesn't work very well for longer 'keywords' (mainly the new-fangled sql-92 stuff). Perhaps a redefinition of what constitutes a master keyword would do better.

EA2: Formatter issues

1) Formatter in the worksheet doesn't leave a blank line between sql statements.
If you have several statements in worksheet and format them, they are all formatted as one with no gap between them.
2) You can't just format the selection. If I select a statement and format, the whole worksheet is formatted.
3) It doesn't handle syntax errors.
I think the formatter should detect and report syntax errors (it is a parser after all).
In my worksheet, one of the statements had a syntax error (semi colon inside the parentheses of a sub-query instead of outside), and later statements in the worksheet are indented relative to the statement with the error. AFAICS, the subsequent statements are formatted correctly, but the left margin isn't reset after the error statement.

I agree with smitjb's statements. The formatter has other flaws as well like:
1) Columns and tables are simply indented based on the indentation setting rather than left aligned 1 space after the leading SELECT
2) [INNER, LEFT, RIGHT, FULL [OUTER]] JOIN statements are not right aligned with the select key word the same was as the FROM and WHERE key words
3) GROUP BY and ORDER BY are not aligned with the SELECT key word on the space between GROUP/ORDER and BY, alternatively, the SELECT, FROM and WHERE key words are not indented suffciently to right align with the BY key word.
Setting the formatter indent to 8 cause columns and table to line up 1 space to the right of the SELECT statement, but then nesting of PL/SQL statements shifts to the right very quickly. Perhaps these could be separate indents.
Selecting the option to have a line break follow select from and where statements is not preserved so is not honored.

TOC formattting issue

I've been using framemaker for over 10 years, and I have a nagging problem in TOC's.
Give that you want standard toc's such as:
1.1 Introduction........................................1.3
Simply put, when you generate your TOC in a book, there may be times when the "paratext" is quite long and it causes the text to get to close to the page number or even wraps over to the next line.
For example:
1.1 Introduction to Framemaker 9.0 basics1.3
1.1 The small brown fox jumped over the b
      arrel1.1
How can we set up the heading1TOC parastyle to maintain a distance from the page number and if the paratext is to long, wrap to the next line and put the page number on the far right side.
my basic heading1toc style is set as follows:
Tab stops: 1.375 left
                 6.25 right (with leader ....)
on the reference pages, the heading1toc is
<$paranum> <$paratext>.................<$pagenum>
How can I set it to always "wrap" the text, say for example, when it reachs 6.00 inch so the above example would result in
1.1 Introduction to Framemaker 9.0 basics...1.3
1.1 The small brown fox jumped over the b
      arrel....................................................1.3
Anybody have a solution?

Archive guy wrote:
I've been using framemaker for over 10 years, and I have a nagging problem in TOC's.
Give that you want standard toc's such as:
1.1 Introduction........................................1.3
Simply put, when you generate your TOC in a book, there may be times when the "paratext" is quite long and it causes the text to get to close to the page number or even wraps over to the next line.
For example:
1.1 Introduction to Framemaker 9.0 basics1.3
1.1 The small brown fox jumped over the b
      arrel1.1
How can we set up the heading1TOC parastyle to maintain a distance from the page number and if the paratext is to long, wrap to the next line and put the page number on the far right side.
my basic heading1toc style is set as follows:
Tab stops: 1.375 left
                 6.25 right (with leader ....)
on the reference pages, the heading1toc is
<$paranum> <$paratext>.................<$pagenum>
How can I set it to always "wrap" the text, say for example, when it reachs 6.00 inch so the above example would result in
1.1 Introduction to Framemaker 9.0 basics...1.3
1.1 The small brown fox jumped over the b
      arrel....................................................1.3
Anybody have a solution?
This is an often-posted question. You can find past solutions with aGoogle search for "framemaker toc wrap long lines" and similar phrases, without quotes.
HTH
Regards,
Peter Gold
KnowHow ProServices

BIZTALK EDIFACT decimal point issues

HI,
Am getting below error when i pass my EDIFACT file.
SegmentID: MEA
Position in TS: 337
Data Element ID: C17402
Position in Segment: 4
Position in Field: 2
Data Value: 11.557
37: Invalid character(s) found in data element
I have defined the properties for that in below image.
c17402 datatype is EDIFACT_N, does it allow decimals?or could you please tell me where am making wrong?

I already told you:
You would need to change the EFactDelimiter to:
0x3A, 0x2B, 0x2E, 0x3F, 0x20, 0x27
instead of
0x3A, 0x2B, 0x2C, 0x3F, 0x20, 0x27
Morten la Cour

Help needed with referencing single Excel cells and formatting resulting text

In InDesign CS5 I am putting together a 20pp catalogue of about 200 products. The plan is to have the product information, SKU code, quantity etc fixed, but have the prices (there are two i.e. pack price and individual price) being linked to an Excel spreadsheet. This is so that the prices can be updated in the Excel file and the InDesign file will pull the new prices through. In case you are wondering why I don't pull the whole set of information through, this is because there are a lot of copywriting changes done to the information once it's in InDesign - it's only going to be the prices that will be updated.
I am planning on having two single cell tables in their own text frame, duly formatted with cell style, table style and paragraph style for the two price variables. This I am then going to have to repeat 200 times making sure I link to the next row down in Excel. This is going to be a hideous task but I see know way of modifying the cell in InDesign to point it to the next row in Excel. That's my first problem.
My second problem is this. In the Excel sheet, the prices are formatted as UK currency and are therefore like this...
£2.00
£0.40
£1.43
£9.99
£0.99
£0.09
What I will require is once I import that data (and refresh the data via a newly saved Excel file) is that the prices end up like this...
£2.00
40p
£1.43
£9.99
99p
9p
So if the value is lower than £1.00 it needs a trailing 'p' added and the leading zero and '£' sign stripped off. If the value is lower than £0.10 it also needs the zero after the decimal point stripping off.
Then formatting wise, the '£' sign needs to be superscripted and the same for the 'p'. This I am assuming could be done via GREP?
In summary, can anyone help with the first task of referecing the Excel cells on a cell by cell basis, given that it is the same cell column each time, but the next row down, and also point me in the right direction of the price formattting issues.
Any help will be gratefully received.

I would do this:
Create on line with the formatting.
Export as InDesign tagged text (TXT)
Read out these tags
In Excel exists a function to connect text from several cells and predfined text, there connect the content from cells with the paragraph styling tags. Do it in a seperate sheet. (Better would be to use a database like Access, there you can link your Excel sheet).
Export this sheet as txt file
Place this sheet as tagged text (there is an option in one of the sialog boxes).
In preferences < file handling you can specify that Tablecalculation Sheets and text is not embedded but linked, turn it on.

Decimal formatter issue

Similar Messages

Maybe you are looking for