Visual Basic, mci32.ocx license problem

mci32.ocx license problem

Author	Message
Douglas Marquard #1 / 10	mci32.ocx license problem Hi Bruce: Quote: >License information for this component not found. You don't have an >appropriate license to use this functionality in the design environment >(Error 429) I had this confirmed by MS support staff -- this is a bug in the VB5 setup. If you already have a vb application installed with any of the Service Pack controls, and then try and install VB5, it will not properly update the registry with license info for that control. One workaround is to unregister and delete/move the ocx and then reinstall VB5 (and the latest service pack). Hope this helps, Doug.
Sun, 02 Jul 2000 03:00:00 GMT

J.Scholte #2 / 10	mci32.ocx license problem I had the same problem and got the solution from this group. First uninstal vb5.0 restart, then create a dir called c:\ocx copy all the .ocx files from windows\system to this dir, then instal vb50 restart, run the servicepack, restart, copy all of the .ocx files back to windows\system if asked file exist overwrite select no, on my computers it worked. regards, Hans Scholten Douglas Marquardt heeft geschreven in bericht ... Quote: >Hi Bruce: >>License information for this component not found. You don't have an >>appropriate license to use this functionality in the design environment >>(Error 429) >I had this confirmed by MS support staff -- this is a bug in the VB5 setup. >If you already have a vb application installed with any of the Service Pack >controls, and then try and install VB5, it will not properly update the >registry with license info for that control. One workaround is to >unregister and delete/move the ocx and then reinstall VB5 (and the latest >service pack). >Hope this helps, >Doug.
Sun, 02 Jul 2000 03:00:00 GMT

Dan Douce #3 / 10	mci32.ocx license problem I'm having a similar problem but it's with the Connection Designer. MSCONDES.DLL is the file in question and I receive the License error described in the previous messages. I tried your fix (double clicking the REG file) but that didn't seem to do anything. Originally I didn't even have access to the Designer in the components window however I ran regsvr32.exe on MSCONDES.DLL and that at least gave the option on the designers tab in the components window. Have you heard anything related to this problem? Is it the same problem as the OCX licensing problem? Any help would be greatly appreciated. Dan Doucet Quote: >I just found the answer in a post about a similar question: > ----------------- > Double-click on the .REG file in the Tools\Controls directory >of your > install CD. > -- > Jonas > TRION Technologies (www.trion.com) > ------------------------ >Bruce Halpern
Fri, 07 Jul 2000 03:00:00 GMT

Page 1 of 1

[ 10 post ]