Hey, how's it going?

>> He has installed both VFP6t.dll and VFP6r.dll

How were the VFP .dlls installed? Were they just copied to the server or was the VFP Setup Wizard used to create an installation?

>Okay, I've taken the first baby step into using COM objects. Just like a baby I've fallen flat on my face <g>.
>
>I've just spent the last two weeks creating this wonderful class that culls data from several tables, sends to results to wwXML and returns a beautiful XML document. I've registered it on my local machine and it runs perfectly.
>
>the dll is called BAM.DLL
>
>I've handed it over to the Server guy who has attempted to regsrv32 it on the NT server and it fails: "Failed Return Code was ox80004005".
>
>I'm using VFP 6.0 SP4 version 06.00.8862.00
>The server is running NT 4.0 SP6a
>
>He has installed both VFP6t.dll and VFP6r.dll
>
>He has received the BAM.DLL install error before either runtimes were installed. He then installed the vfp6t.dll which installed perfectly. Then attempted to install the bam.dll and it errored out. The vfp6r.dll was then installed and then again attempted to install BAM.dll, again it errored out.
>
>both vfp6t & vfp6r are currently installed on the server.
>
>bam.dll was created as a Multi-threaded COM server.
>
>To check my sanity, I've also created a completely seperate fakecom.dll with only one class & one method. This method's only job is to return the text string "The computer hates you!"
>
>This dll also works on my computer, but error's out with the above error message also.
>
>Please Help, for I have gone insane.
>
>Ken