>>Hi folks. In the last few weeks we've converted our ASP.NET 2.0 application to use VFP9SP1 OLEDB provider instead of COM components. Though very fast, we are getting some errors that appear to be false.
>>
>>Errors such as:
>>- cannot find table zero
>>- database is invalid, please validate
>>- index is corrupt
>>
>>When I open the tables or database with VFP9SP1 and validate them they are fine. I've tried to pin this down in our test environment and on our server, but the errors happend sporadically on the exact same code.
>>
>>Finally, my questions:
>>- Is this version of the OLEDB provider flakey?
>>- Has anyone else deployed ASP.NET 2.0 and the latest VFP OLEDB provider? What is your experience?
>>- Is the VFP8 OLEDB more stable?
>
>I'm still getting some odd errors. Nothing reproducible in a regular way. One server that is running Win2003 doesn't throw any errors, but the server running Win2000 does. The setup is indentical on both servers.
What version of MDAC is on each box?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up