G
Guest
Hi all,
I am trying to do a simple table export to a text file in Access 2003. The
data has numeric values with multiple digits to the right of the decimal
point (ex: 25.2687). The data is stored as a number / double. When I do the
export to a comma demitted file the digits after the hundredths place gets
dropped (ex: 25.2687 becomes 25.26). The wizard shows the data correctly in
the viewer. The data appears correctly in the data view and queries. But
when I view the generated text file the data is missing.
Am I missing something here? Is this a bug? If so isn’t the ability to
import and export data between Access and some other enterprise database part
of the core uses of Access? I know one workaround is to change the numeric
field to text and then export. But I really want a fix or and explanation
that this is user error. Ideas/Help?
Thanks in advance,
Andy
PS: I read the following on the Help and Support page but it’s not exactly
the same thing. Plus it gives a similar workaround but no mention of solving
the problem.
http://support.microsoft.com/?scid=kb;en-us;301915&spid=2509&sid=50
I am trying to do a simple table export to a text file in Access 2003. The
data has numeric values with multiple digits to the right of the decimal
point (ex: 25.2687). The data is stored as a number / double. When I do the
export to a comma demitted file the digits after the hundredths place gets
dropped (ex: 25.2687 becomes 25.26). The wizard shows the data correctly in
the viewer. The data appears correctly in the data view and queries. But
when I view the generated text file the data is missing.
Am I missing something here? Is this a bug? If so isn’t the ability to
import and export data between Access and some other enterprise database part
of the core uses of Access? I know one workaround is to change the numeric
field to text and then export. But I really want a fix or and explanation
that this is user error. Ideas/Help?
Thanks in advance,
Andy
PS: I read the following on the Help and Support page but it’s not exactly
the same thing. Plus it gives a similar workaround but no mention of solving
the problem.
http://support.microsoft.com/?scid=kb;en-us;301915&spid=2509&sid=50