I still don't entirely understand the issue. I do notice that you are using smalldatetime. I have found that if you stray beyond char, varchar, bit, datetime, int, dec - essentially, the basic data types, you can run into problems in VFP. Again, I don't understand what is "wrong". Are you encountering an error. Is the data getting munged up? What exactly is the problem? What exactly is wrong?

One suggestion would be be is to use the basic datetime type in SQL...

Other than that, you will need to give me more detailed info...

< JVP >


>The current date is being entered in place of the date in the field. This data is comming from a SQL 7 database using SQLE(...). The orig datatype is smalldatetime. This only happens when I get a result set from SQL, VFP tables with a DateTime field seem to work ok. I can't really go straight to ADO from SQL since I need to do some touching up and join in some VFP lookup data before passing the ADO rs on.
>
>Bill
>
>>Hi Bill..
>>
>>When you say the DateTime Fields are wrong, what do you mean by "wrong"?
>>
>>Unless one knows what is wrong, one cannot know the issue...< bg >...
>>
>>< JVP >
>>
>>
>>>I am creating Crystal Reports for my web site now. Whenever I use cur2rs to convert my cursor to ado to pass to the CR report, all the DateTime fields are wrong. Is this a know issue? Is there a work around? Now I do a second query with a TTOD() on any datetime fields.
>>>
>>>TIA
>>>Bill