Hi,
I have also made several ocxs myself and had used them in my programs. The problem is the deployment of the programs. How will I know if all my ocxs are registered in the computers to which they are supposed to run?
Printable View
Hi,
I have also made several ocxs myself and had used them in my programs. The problem is the deployment of the programs. How will I know if all my ocxs are registered in the computers to which they are supposed to run?
You won't get any errors. :DQuote:
Originally posted by ripple214
How will I know if all my ocxs are registered in the computers to which they are supposed to run?
Just make sure you include them while packaging. That should be enough.
I hate to be rude, but isn't that what my question is for. If my programs are to be deployed, they must not have runtime errors. That's why I need to know if all my ocxs are registered. I mean I just can't wait until my program gives an error message just to know that the ocx is not registered. I need to know if all of them are registered during the start of my programs.
As mendhak says, just use an installation to make sure the components are copied and registered. If users manually unregister them, it's not your fault. ;)
The only other solution I can think of is having a small executable that does not use the to-be-checked ActiveX controls to check if the controls are registered and available. If they are, the main app is started, otherwise the user is notified. :)
ahh say you could find out if an ocx was not registered.. what exactly would you do about it? tell the user which file is missing? this is exactly what happens already
Well, you should at least tell them that the file is missing. :) If you want to make your app more user-friendly, you could automatically download the missing files (either from MS or perhaps from your own server if you have one) and install/register them. Or you could ask for the application CD and copy them from there if your app was distributed that way. :)
Use the Package and Deployment program provided with VB or use a 3rd party version. Either way, all you have to do is tell the package to include your OCX and it will gather all the needed files ona install/register everything for you. You should have no problems.
Why are you trying to make it more complicated than it is?