Phil
This is a known issue, plenty of people (me included) have been caught out
with it.
Try checking MSDN

I cant even remember how we got around it I'm afraid, but I think that
assuming US dates may get around it. I think maybe VBA or Access (or maybe
Excel!) is stuck in US locale for dates or something.

This fella may help
http://allenbrowne.com/ser-36.html



cheers
Simon


"RS200Phil" wrote:

Thanks for the ideas, Gareth.

We are importing data from about 50 different clients and unfortunately,
do not have control over the date formatting on their systems. This is
the only client who sends the field as a date. All the others either
send it as a text field (as you suggested and I have requested) or in
CSV format (much preferred!).

I'm using the "Transferspreadsheet" method in the VBA code to transfer
the data into a holding table. I then carry out a little pre-processing
before INSERTING data from this table into the "live" destination.

I have tried importing the field into text field (wrong dates), a date
field (ditto) or a numeric (data type conversion failure). I had
planned to use the numeric to perform my own date-offsetting!!!

So basically, I'm still a bit low on ideas.

Thanks again for your help, though. Good advice.

Cheers

Phil


*** Sent via Developersdex http://www.developersdex.com ***