Results 1 to 7 of 7

Thread: VB reckons none of my ocx, oca, dll are registered?

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Jun 1999
    Location
    Brisbane, Qld, Australia
    Posts
    78

    Angry

    Hi,

    I had to reformat my hdd today and reinstalled VB. My problem is that of course it rejects the progra i have been working on for 10 months. It reckons that i dont have a licence for some of the oca, ocx, etc that all come with the proper VB package. I have tried reinstalling VB but it has the same problem. Any ideas on what to do? Any help would definitely be appreciated and thanx in advance

    Mike

  2. #2
    Addicted Member
    Join Date
    Mar 2000
    Location
    Gainesville, FL
    Posts
    131
    Make sure you have all service packs installed. If that does not work, reinstall windows and reinstall vb. That worked for me when I had that problem!

  3. #3
    Lively Member
    Join Date
    Jan 1999
    Location
    Rochester NY, USA
    Posts
    93
    did you by chance reinstall your the app you're making before you installed VB? Here's what happens..

    When you install an app that has ocx's and vbx's, they are installed _without_ a licence to use them for defelopment. When you install VB, it installs them with the ability to use them for development. Here's where the problem is..

    You install your app (or any other app) that had the same or newer version of the control and it installs without the ability to use it for development. Now when VB installs, it looks at that file and sees that either it's up to date or that it's newer than what it's going to install and doesn't install it. There's actually a KB article on Mirosofts web site about how to get around it. You're going to have to uninstall VB and the app that has those controls, unregister the files with regsvr32 and then reinstall VB, Then I'd add all the servicepaks and then reinstall the app.

    I just did some searching and found the article.. it should save you a format

    http://support.microsoft.com/support...-US&SD=gn&FR=0

  4. #4
    Fanatic Member
    Join Date
    Jan 2000
    Location
    Nitro
    Posts
    633
    Chemically Formulated As:
    Dr. Nitro

  5. #5
    Guest
    Instead of re-installing VB, I'd suggest that you compelety remove VB from your system and then install it again, as if it was your first time. This always works for me.

  6. #6
    Addicted Member jcouture100's Avatar
    Join Date
    Aug 1999
    Posts
    141

    Smile

    You might want to check out this info on the Microsoft site.
    They have posted fixes for various control licensing problems.

    Q195353 - FILE: VBUSC.EXE Provides Licensing for Discontinued Controls

    Q194751 - FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0

    Hope this helps.
    JC

  7. #7
    Guest

    no dont reinstall!

    i had this same problem were about half the controls were not registered or lisenced. but reinstalling does nothing to it, it has to do with the registery settings. if you check microsoft.com you will find a solution to your problem, you have to download a 1.x meg file that fixes ALL lisence errors. i forgot the exact link but it took me a VERY long time to find. if you cant find it, email me and ill send the program cause i put it on a disk.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width