>
>Hmmmm. I guess it begs the question of why you are converting the date to a char type.
>
>Again, I tested on a local view. The field still comes back as a char type. Why don't you post your ADO code...


Hej John,

We´ve had a lot of trouble with Excel / ADO and numeric & date datatypes, VBA or whatever actually errors out when fed with plain numerics so we had to use DOUBLE instead, and Excel does not seem to like VFP date types much either, we´ve seen som pretty bizarre results.

There is not much to the code, so I am going to take the liberty of sending you a screendump from the VBA debugger which illustrates the problem instead.
Can´t attach a file here, so it´ll have to be e-mail.

Bearing in mind that I expect ANSI YYYY.MM.DD notation, this clearly indicates that ADO does something unexpected with the data.

Appreciate you taking the time!