>Do you open and close a connection for each of these SQLs? If so maybe you could group some of them to share the same connection. Is all of the data really that volatile - maybe some of it could be cached?

This may apply on some places and not on other places. Also, the data class is simply fantastic as what it does and this means I have a lot of properties and methods in there. So, basically, one SQL command is usually one instance of the class.

>I wouldn't bet on anything happening soon :-{ My guess is that the VFPOLEDB dll would need modifying....

This is what we discussed again yesterday on phone with Microsoft. By now, they are well aware that we cannot deploy applications like that in production if we want to keep VFP as the backend. I told them that it would be a shame that developers would have to leave VFP in favour of SQL Server just because the VFPOleDb cannot handle it. They all agree that a resolution to the issue should be done asap.

>Keeping the application lock in place for the entire life of a connection seems to eliminate the errors completely.
>IAC, I'd suggest you test this - it may be that the performance hit is not as great as you anticipate.

Thanks