Hi John Petersen,

Sorry about the spelling error, no "rip" intended -mental note: use cut-n-paste.

Why didn't I address your assertions directly? First, I'm well aware of your reputation for accuracy and did not take your statement as an assertion but as fact. Second, I had planned to reply to you with other questions; if needed, after I had researched the problem.

I'm using ADO with ASP to drive an Intranet. Nothing unique here, ADO to access VFP tables as well as other data sources. I have not upgraded our server with version 2.0 yet and this may be the reason numeric access is working. Also, best that I can recall I am accessing VFP and FPW 2.6 free tables only. To-date, all VFP database access has been though middle tier's. For VFP application tables, your solution to convert numeric field types to double will be applied. Unfortunately, conversion of other tables will not be so simple.

We also access many FPW 2.6 tables which do not support the double field type. Is there an easy workaround here? We do use a lot of VFP OLE servers with ASP when intensive data processing is required, but I would hate to use this approach to simply query a table or update a record. I don't mind for future applications but backtracking to fix all existing code will require a lot of time.

Since Microsoft has acknowledged this as a bug, do you know if they intend to fix it?

Regards,
Mike