Hi Tim,

I can think of two approaches to this.

1) If importing into Currency fields, I'd try using a schema.ini file
instead of an import specification. Schema.ini exposes more settings
than the import/export wizard; I'd experiment with something like this
for the currency settings in the schema.ini entry for the file:

CurrencySymbol=
CurrencyPosFormat=0
CurrencyDigits=2
CurrencyNegFormat=0
CurrencyThousandSymbol=.
CurrencyDecimalSymbol=,

though I find the documentation on CurrencyPosFormat and
CurrencyNegFormat very confusing.

For more on schema.ini, see:
Create a Schema.ini file based on an existing table in your database:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;155512
How to Use Schema.ini for Accessing Text Data
http://support.microsoft.com/default.aspx?scid=kb;EN-US;149090

For details of the Schema.ini settings, see the Help topic "Initializing
the Text Data Source Driver", which is also online at
http://office.microsoft.com/en-us/assistance/HP010321661033.aspx
The schema.ini stuff is a long way from the start of the document.
See also (or alternatively, I can't work out which)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcje
tschema_ini_file.asp

2) Import the file into a "staging" table in which these fields are
defined as text; then use an append query to move the data from the
staging table into the table where you want it. Use a calculated field
in the query to convert the text string into the currency or number type
you need, e.g. something like this:

    CurrencyValue: CCur(Replace(Replace([TextValue],".",""), ",", "."))

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.