>The common denominator seems to be that all the errors are from the OLEDB provider. If the errors stemmed from multiple page based objects using global functions then I'd expect to see some errors that were not VFPOLEDB related (but that's just an assumption - maybe your oApp has few functions that are not ADO related - and those may suffer corruption without error).

Yes, the problem is really about either the OleDd .NET objects or the VFP data provider.