|
I have done more trouble shooting and it appears this related to the fact that the "Field Size" in the table created by the Import is
"Decimal" and the Export / Import filters from MS do not like this. Other than the obvious of changing the Field Type to "Long Integer"
does anyone have a tip on how to convert the data element so Export will function.
I have tried setting Format to General & Fixed, neither helped ? Do I need to put a Function behind the Format ?
TIA, JMS..
At 11:01 AM 10/8/2003, Jeff Silberberg wrote:Morning All,
Have a strange problem that I hope someone here has resolved.
Created an Empty mdb with Microsoft Access 2K
Imported Contents of iSeries PF into the MDB. (Created an Populated Table no Problem.)
Then tried to get additional data two days latter and import using CSV created with a CPYTOIMPF. But when I try and import this resulting CSV,
I get an error message, and in fact if I try and export the data from working MDB table to a CSV, I also get an Attribute error message.
Limited help messages appeared to indicate that my decimal representation in the systems "regional" settings did not match Access. But I don't see any obvious problems.
Anyone seen / know how to resolve this ??
TIA, JMS... _______________________________________________
Jeffrey Silberberg CompuDesigns, Inc. Atlanta, GA. 30350
_______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.