That is somewhat of a problem because the application is already distributed. I am working on an update to the current app. Install Shield would be my first stop in the package.

I am open to another option. I can provide the OCX file in the application folder and all I need to do is have the prg check to see if it is registered, if it is not then I will register it for them and continue the prg. Does anyone have any example code on how to scan and register an OCX file on a client machine?

TIA

WEs


>It depends on what tool you're using to distribute your applications.
>
>>I am using an SMTP program that is included in my project that is referenced by a function. The SMTP program uses the mswinsck.ocx file that is usually located in the System32 folder. I need to figure out how to package the mswinsck.ocx file with the exe or inlcude it in the application folder. The reason for this is that many people (the clients that use this system in question) do not have the mswinsck.ocx file on their computer so they receive errors when trying to run the program. I was given an example of how to do this in VB but it involves specific features of the editor and not source code. Any help would be appreciated. Thanks
>>
>>Wes