This is my first foray into building ActiveX dll's, so maybe I'm missing something very fundamental. Please bear with me.
My development machine is a Windows 2000 Workstation. I'm using VB6 SP5. My application server is Windows 2000 Server. Clients are running either NT 4.0 SP6 or Windows 2000 Workstation.
I created an ActiveX dll project in VB6. It tested out fine. I compiled the dll. Set the compatibility in the project properties to binary. Copied the dll to a test application server. Installed it under Component Services.
Started it up.
I developed a VB6 client - standard exe project. I was able to reference the correct dll through the Project References dialog. It appears as an Reference in the project's vbp file.
I begin to notice trouble when I try to use PDW to create a correct installation script. If I don't pay attention, PDW wants to install the dll I've referenced into my WINNT/System32 directory. If I tell PDW not to install the dll, the client application can't see the dll on the server machine. And I can't seem to find any options to retain the reference to the dll.
Can anyone help me with this?
My development machine is a Windows 2000 Workstation. I'm using VB6 SP5. My application server is Windows 2000 Server. Clients are running either NT 4.0 SP6 or Windows 2000 Workstation.
I created an ActiveX dll project in VB6. It tested out fine. I compiled the dll. Set the compatibility in the project properties to binary. Copied the dll to a test application server. Installed it under Component Services.
Started it up.
I developed a VB6 client - standard exe project. I was able to reference the correct dll through the Project References dialog. It appears as an Reference in the project's vbp file.
I begin to notice trouble when I try to use PDW to create a correct installation script. If I don't pay attention, PDW wants to install the dll I've referenced into my WINNT/System32 directory. If I tell PDW not to install the dll, the client application can't see the dll on the server machine. And I can't seem to find any options to retain the reference to the dll.
Can anyone help me with this?