We are using Excel Com Add in on 2010 and 2013 and this is causing intermittent adding of a ZERO to some numeric data we are downloading from AS/400.
We are not sure if this is an AS/400 issue (OS v6.1) and Client Access v5.8 upwards?
Any ideas what might be causing this?
This sounds familiar to me, but I am coming up just shy of recalling this. Is it adding leading or trailing 0s? Is the data field on the i a text or numeric (packed? maybe) data type? Is the zero being added to the same field in all records?
doesn't sound like the issue we had; but it has been a while. Sorry.
I think the issue we had was numeric data in an apha field and the transfer was trying to make into a numeric field and adding trailing zeros or something like that.
What are the field definitions of the successful and unsuccessful exports? Could it have anything to do with the field defined with an even number of digits, such as 6,2?
How is the field defied in the DDS on the I-series? If no DDS was this created via SQL?
You also mentioned that on a second attempt it worked. I am curious if it always works on a second attempt? It may have something to do with the FDF that gets created as part of the transfer process.
The data that has been tested has been from a program output to a PF, we have downloaded this using the Excel COM add-in. We don't make any adjustments when downloading "direct" from Excel so don't know if the FDF is even created
The other weird issue it has never been a problem on my machine, the difference is I use WRKQRY a lot.
We have investigated different combinations of Excel and Client Access versions to ensure latest updates\incompatibilities.
Not sure what is happening - just thought that maybe when a programmer "writes" to a file maybe there is something subtly different they can \ need to change!?
Discuss This Question: 11  Replies
azohawk - it seems to add a "zero" however when you download the data a second time it disappears - very random?
doesn't sound like the issue we had; but it has been a while. Sorry.
I think the issue we had was numeric data in an apha field and the transfer was trying to make into a numeric field and adding trailing zeros or something like that.
I thought the user had formatted the Excel and then imported the data, but it happens on a blank spreadsheet.
I then thought maybe the programmer had "written" the data to the file different to other programmers but not sure that's true either!
THANKS for replying anyway :-)
WoodEngineer - thanks for your response, does this matter if it looks okay on the AS400 (viewing through WRKQRY and DSPPFM) .
From a download point of view using the COM add-in = we are not changing the download at all
How is the field defied in the DDS on the I-series? If no DDS was this created via SQL?
You also mentioned that on a second attempt it worked. I am curious if it always works on a second attempt? It may have something to do with the FDF that gets created as part of the transfer process.
ToddN2000 thanks for your reply
The data that has been tested has been from a program output to a PF, we have downloaded this using the Excel COM add-in. We don't make any adjustments when downloading "direct" from Excel so don't know if the FDF is even created
The other weird issue it has never been a problem on my machine, the difference is I use WRKQRY a lot.
We have investigated different combinations of Excel and Client Access versions to ensure latest updates\incompatibilities.
Not sure what is happening - just thought that maybe when a programmer "writes" to a file maybe there is something subtly different they can \ need to change!?