Nobody replied, so I guess I'll answer to myself.

I found the answer to the first question!


There is a bug in VFP 6.0 sp3 when it comes to creating the vbr file.
If you don't specify a description for the public class in a COM/DCOM environment, then VFP will generate 2 lines in the vbr file that end with '=' sign and no text afterwards. The registration software 'clireg32' doesn't like that.
On the other hand if you enter a description like I did, then those 2 lines will have the description text after the '=' signs on those same lines.

Then VFP CreateObject() function doesn't like it, givin you the error:
"Resource file version mismatch"

I then commented those 2 lines out with (;) symbol and was able to register the dll with clireg32 and I didn't get the error above. I still get the next error about the class not being registered which I'm working on. See my previous post for explanation.

Any help ?