We're using a server based VB DCOM object to communicate data with VFP client in ADO recordsets. This seems to work fine on about 700 installations (but of course - one).

This install is running Windows ME, 128 mb Ram, and until recently was also working fine. Within the last two weeks something has happened to cause them to receive C5 exception errors in non-consistant locations in our VFP app, and only after running DCOM. If we reboot the system after the DCOM transmission, everythings okey-dokey.

I've replaced all the dll's we access, poured over the code to make sure everything was being released, checked MSDN, but can't find any answers. I believe that some piece of code external to the app must have been corrupted ( or memory problems exist) but can't isolate either.

Anyone ever run into this ????

TIA.