Subject: Make exe files
Posted By: MikeJames42 Post Date: 2/11/2004 8:47:35 AM
I have recently upgraded from Visual BAsic 6 Working model to the full Visual Studio Enterprise edition. However when trying to make exe files I get an error stating that I do not have the correct license information. Can anyone help overcome this problem?

Thanks

Reply By: Yehuda Reply Date: 2/11/2004 8:58:36 AM
Did you uninstall the working model first?  If not, uninstall everything and reinstall the Enterprise edition.  It also might help to do a registry cleanup in between (a free registry cleanup tool can be obtained at http://download.com.com/3000-2094-881470.html?tag=list).

Yehuda
Reply By: MikeJames42 Reply Date: 2/11/2004 10:09:37 AM

Yehuda thanks for that. I've unistalled the working model first and ran a registry cleanup. I've just uninstalled everything again and reinstalled it and get the following message while trying to make an exe file:

License information for this component cannot be found. You do not have an appropriate license to use this functionality within the design environment

The version of Visual Studio has installed correctly on a colleagues PC and works fine. Any otehr suggestions.

Reply By: Yehuda Reply Date: 2/11/2004 10:26:13 AM
Look at this article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;194751
Reply By: MikeJames42 Reply Date: 2/11/2004 10:28:50 AM
Tried it and it doesn't work unfortunately.

Reply By: Yehuda Reply Date: 2/11/2004 10:36:12 AM
Have you tried just opening a form (no other activeX compoonents referenced) and compiling it.  Your error is usually thrown when compiling a project referencing ActiveX controls marked for licencing that aren't licensed properly.
Reply By: MikeJames42 Reply Date: 2/11/2004 10:42:13 AM
Just tried it and can make an executable for a blank form with no activeX components. IS there anyway of finding out which ActiveX components aren't licensed properly?

Thanks for you help on this.

Reply By: Yehuda Reply Date: 2/11/2004 10:50:32 AM
What Components are you referencing?  Usually it is an ActiveX Control.
Reply By: MikeJames42 Reply Date: 2/11/2004 11:14:35 AM

I have been through the controls tab within the components option and made sure that all the .ocx files are registered. I tried to do the same with the dll's within the DEsigner tab but kept getting error messages. Could this be the route of the proble?

Reply By: Yehuda Reply Date: 2/11/2004 1:50:27 PM
Possibly.  It depends on the error message (remember not all DLLs are COM DLLs which can be registered).  Have you tried again after registering all OCRs?
Reply By: marcostraf Reply Date: 2/11/2004 2:43:39 PM
Mike,
are you using third party components?
Even if the components are registered does not mean that you can use it for compile. Components come in two ways: the development version (that you use to compile) and the distribuitable version (that you include in your distribution package). This inhibits your client to make executable using that component (that they did not buy).
It is possible that the process of upgrading overwrote one of your development components, and it not easy to say each one... Try adding your third party component one by one in your test application, painful. If you find the wrong one, you have to reinstall it.
Reply By: MikeJames42 Reply Date: 2/12/2004 4:38:27 AM
Thanks to everyone for their help, the ViewPro ActiveX control wasn't registered for some reason.


Go to topic 9715

Return to index page 950
Return to index page 949
Return to index page 948
Return to index page 947
Return to index page 946
Return to index page 945
Return to index page 944
Return to index page 943
Return to index page 942
Return to index page 941