>Has anyone ever received some memory problems when using VFPOleDb with .NET to access VFP data? On the test server, I never had that problem. But, on the production server, since the last two weeks, this problem has arrived and this is happening like three times a day. Everyone is trying to find the cause of the problem. At first, we thought this could have been related to extensive processes that are running on the same server. Everytime the problem was happening, we were able to associate a corelation with those processes. Then, they tried to slow down those applications a little bit and even to shut them down. They also moved the Web site into another drive. Now, this is happening also when there is nothing running at all on the server but the Web site and also when there is practically no traffic. We do not know yet what is the cause of the problem. Could it be that there is really a memory problem with the VFPOleDb data provider when the size of some tables are reaching a certain
>limit, something in regards to specific tag such as using UPPER(), the number of fields, the number of tags, etc?
>
>We have not reached yet the point of our full migration to SQL Server. So, for the next 8 weeks, we have to live with that. But, this is causing a fortune at various levels such as monitoring, adjustments, troubleshooting, problems it causes with the data and so on. Also, we have no guaranty that moving to SQL Server will resolve the issue as we have no idea what the problem is.

I have an ASP.NET application residing on number of customers' web servers and each one is using VfpOleDb driver to access VFP data. I have not had any reports of the memory problem from any of the customers.

I wonder, how does the memory problem manifest itself?