S
Sparky
Has anyone else had an issue with decimal truncation when performing a table
import (from text). I have a text file that I import into an already
existing table. The data source has integers (0, 9, etc) and decimals (7.9,
19.99, etc). I am noticing that if the first couple of records are integers,
then Access 2007 is assuming that all records for that collumn are integers
and it truncates the decimals.
If I switch the record order and load the decimal records first then the
decimals do not get truncated. If I place the .00 on my input file then the
decimals do not get truncated. But, neither of these are viable options for
my data application.
Being the table is pre-existing, I have tried pre-defining the fields as
double, and even forced 2 decimal locations - but to no avail, the system
truncates the decimal and then appends a .00 !
This was not an issue in Access 2003, as my data source has not changed...
but it is happening repeatedly in Access 2007. Ideas? Suggestions?
import (from text). I have a text file that I import into an already
existing table. The data source has integers (0, 9, etc) and decimals (7.9,
19.99, etc). I am noticing that if the first couple of records are integers,
then Access 2007 is assuming that all records for that collumn are integers
and it truncates the decimals.
If I switch the record order and load the decimal records first then the
decimals do not get truncated. If I place the .00 on my input file then the
decimals do not get truncated. But, neither of these are viable options for
my data application.
Being the table is pre-existing, I have tried pre-defining the fields as
double, and even forced 2 decimal locations - but to no avail, the system
truncates the decimal and then appends a .00 !
This was not an issue in Access 2003, as my data source has not changed...
but it is happening repeatedly in Access 2007. Ideas? Suggestions?