Hi Michael....

I can understand your frustation. On the whole, VFP numerics and ADO are not compatible. Try this test:

1. Create a System DSN pointing to the TasTraders Database that ships with VFP
2. Issue these lines of code:

oconn = createobject("adodb.connection")
ors = createobject("adodb.recordset")
oconn.Open("tastrade")
ors.open("select * From orders",oconn,3,4)
ors.fields("discount").value = 11
ors.updatebatch && kaboom, you will get OLE-DB errors

If however, you change the discount field to double, all works fine.

Microsoft has acknowledged this as a bug. There are all sorts of problems with ADO and the VFP ODBC driver. The big problem is with Shaped Recordsets. Microsoft has also acknowledged this problem.

One thing to keep in mind that the version of ADO I am using is 2.0. Perhaps you are using 1.5 and no problems have existed. I have not gone back to the previous version of ADO to test since version 1.5 is irrelevant.

>Watching the John Peterson thread where he stated that ADO does not support
>(not compatible with) numeric field type. What!?? I sure have used a lot of >ADO on VFP numeric fields - Houston, we have a problem. Outside of the numeric >resolution issue, ADO has "appeared" to work fine with numeric fields.

For starters, its PETERSEN - not PETERSON. So, if you are going to rip me here, please do me the courtesy of spelling my name correctly < bg >. Also, why did'nt you address my assertions directly??????

If you would be so kind, would you send me your example of how VFP/Fox numerics are working with ADO. I would like very much to take a peek at it.