D
David
Hello,
I have a databse which imports a set of excel files on a daily basis. When I
run the import routine on my machine, everything works OK, with no import
error tables visible afterwards.
I've now mailed the database to one of our users in the US (I'm in the UK),
and although we have the same version of Access (2003), he is left with
import errors after the process has run. I also ran the same process on a
spare laptop, and this also generated the import errors.
Are there any settings which might lead to - or fix! - this? I do remember
seeing something about a registry setting which dictates how many rows access
checks to assess the likely datatype. But I'd rather avoid this if possible.
Ultimately, this is a data type error, and I know, I know... I should use a
dummy row, etc, but this would be difficult in the circumstances, and it
works on my machine, so there's the possibility of a more definitive solution!
Any suggestions??
Thank you!
I have a databse which imports a set of excel files on a daily basis. When I
run the import routine on my machine, everything works OK, with no import
error tables visible afterwards.
I've now mailed the database to one of our users in the US (I'm in the UK),
and although we have the same version of Access (2003), he is left with
import errors after the process has run. I also ran the same process on a
spare laptop, and this also generated the import errors.
Are there any settings which might lead to - or fix! - this? I do remember
seeing something about a registry setting which dictates how many rows access
checks to assess the likely datatype. But I'd rather avoid this if possible.
Ultimately, this is a data type error, and I know, I know... I should use a
dummy row, etc, but this would be difficult in the circumstances, and it
works on my machine, so there's the possibility of a more definitive solution!
Any suggestions??
Thank you!