HELP! We have a web app that uses the VFP ODBC driver to access a simple VFP table. This works fine... UNTIL a few days have gone by. Suddenly, the ODBC driver will start behaving as if there are NO records in the VFP table. No error messages. No indication whatsoever of any error state. But ALL SQL requests through the driver for ANY VFP table suddenly come back with an empty recordset. The only way to recover is to reboot the OS. Then things work fine again.

We use a simple architecture. Activer Server Page scripts use the VFP ODBC driver via ADO. An ADO recordset is returned. We are using the MDAC version that was distributed with Visual Studio SP3.

Please let me know if anybody out there has seen anything like this! I want to emphasize that the application works GREAT, usually for 2-4 weeks, then BAM!... as if some internal resource is suddenly exhausted or some internal state is reached that the ODBC logic does not expect and is not even aware of. Like I said, NO error messages or error indicators. Just empty recordsets and nothing but empty recordsets.

Thanks very much for any info/suggestions!