I do not have any VB run-time files installed on the target machine. Do I need them? I'm not sure what the minimal list of VB run-time files are that are required for the VB ActiveX DLL to work. Obviously, I don't want to have to install all of Visual Studio :-/

RegSvr32 does not apparently work with ActiveX DLLs. I tried it and got the message: "LoadLibrary ("rtf2html.dll") failed." According to the documentation I read about creating VB ActiveX DLLs the registration should be done programmatically using the "DllRegisterServer()" command, which appears to work fine on Visual Studio machines.


>Mark,
>Do you have the VB run-time files installed on the target machine? What happens when you attempt to register the DLL using Regsvr32 from the Command prompt? Does it register? If not, do you get an informative error?
>
>>I created an ActiveX DLL in VB for use in a VFP application. The application works fine on any machine that has had Visual Studio 6.0 installed on it. But on machines that have only had the VFP runtime files required to run the application installed on them, including the new VB DLL, get the error: "Cannot load 32-bit DLL c:\windows\system\RTF2HTML.DLL".
>>
>>The only aspect of the application that is not working on the "non-Visual Studio" machines is that which pertains to my new VB DLL so I know I have all the "normal" runtime files in place. (I've been doing standalone VFP apps for many years; it's only the introduction of a VB ActiveX DLL that I am new to.)
>>
>>I am programmatically registering the DLL with the "DllRegisterServer()" command in the app.
>>
>>Does anyone have any idea what additional files, that are installed as part of Visual Studio, are necessary for the VB DLL to work?