A very recurrent problem for my...

Don't trust in the package of runtimes. Copy all (Any *FOX*.DLL or TLB or sometrhing like) manually to the afected machine. Try to register again (some must fail, this ok).

If this work, then try to isolate where is the bastart dll.

Also, you use ActiveX? Ocx? For sure this is a problem. VFP is a weak COM player...

If this work in VFP7 and in VFP8 not, look for a resource/memory leak. I find in the transition from VFP6-7 troubles managing ADO Components (again COM here). We stop the move for this. Later, a personal inspect found troubles in the managment of null/realeased (i'm free objects, but this objects NEVER released by VFP) objects (some changes inner versions). Something like can happend now. Check "What is new" and look for cahnges, specially in object, null, com sides.

Maybe first, build 2 total clean forms and run the two modeless, and look if in this simple scenario this work or not. If not, maybe is not a runtime problem, is a changed feature or a bizarre COM trick..