>>Hi, I was silly enough to install IE4 Preview 2 and now most of my active web pages refuse to read the VFoxPro files. I've narrowed the error down to numeric fields. It seems that IE4 PR2 can handle character fields without a problem but gives the ADODB Field Error 80040e21 when you get to a numeric field. I've looked through the registry and it seems that IE4 PR2 installed "ADODB 1.5" presumably replacing ADODB 1.0 (msado10.dll). Does anyone have the same problem? Can anyone suggest a fix other than changing all my numeric fields to characters?
>>
>>Rgds
>>Petras
>
>Petras,
>
>I know of a numeric resolution problem accessing VFP tables via ADO. I found that the numeric width on the Foxpro table must be 1 digit more than the width of the largest numeric value you intend to store. ie:
>maxvalue=9999 then make the VFP field width=5.
>
>Not sure about the versions, I was using Visual Studio release of VFP and ASP. This error occured under Win95 PW Server, have not tested for the error under NT Server running IIS.
>
>HTH
>Mike

Hi, thanks for the response. The same VFP table works fine with the same Win95 PW Server, VFP ODBC driver and IE4 Preview Release 1. It's only stopped working with PR2. I've scoured the Microsoft Support pages and cannot find anything. It almost seems like a brand new problem with IE4 PR2 which is beta afterall.

Rgds
Petras