>Does anyone know if there is a problem with the MS SQL Server 7 provider for ADO that prevents it from dealing with DateTime data types?
>
>In a class I created to import records via an ADO recordset object I cycle through the recordset fields collection and set the values equal to that of matching field in a VFP table. It works fine for all but VFP datetime data types, which cause an error.
>
>The Recordset.Field.Type is 135, which according to the SDK is "adDBTimeStamp - A date-time stamp (yyyymmddhhmmss plus a fraction in billionths) (DBTYPE_DBTIMESTAMP)". This implies that it is a SQL timestamp data type, but a SQL timestamp data type is in effect a binary value, not a date/time value.
>
>Does the incoming value have to be converted somehow? Or is this really a bug in the ADO SQL provider? Anyone know
>
>TIA -
Hmmm. Either I didn't make the problem clear or y'all are too busy putting your .02 in regarding PUTM. If it's the former LMK and I'll try to restate.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
