"country" dependency when importing into acces from csv file

[removethispamfilter]

Hi
Im working in a company where windows systems are set up for
different "countries".

When setting up the "import from csv file" the decimal separator is
set up to "," (the thousands separator is not set) and the text
delimiter is set to "

when users having a windows not based upon this standard in numbers (
in UK it is "." as decimal separator), the access takes the definition
of the country and the import of numbers often fails (or sometimes
worse: multiply the number by 100 so 11 becomes 11 but 11,1 becomes
1110).

Why do access override the definitoin specifically set in access
import "filter"?

Is it really nessecarily to have a macro doing the same?

A.Karbek

[pietlinden]

did you try creating an explicit import specification?

[AndersK]

On 18 Jul 2006 15:53:53 -0700, pi********@hotmail.com wrote:

>did you try creating an explicit import specification?

Yes
It specifically was set to use a speciifc character as a number
decimal (",") which is danish standard (33,22 ) in USA the , is used
as a thousands delimiter.
If the user uses this access base in a XP windows set up country = USA
(and of course then XP are using "." as decimal separator (as in
33.22) then the access base imports 33,22 as 33220 which is really not
good.

Anders