Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SSPanel - License not found error 1

Status
Not open for further replies.

rdeleon

IS-IT--Management
Jun 11, 2002
114
US
I have inherited a VB/SQL program that I have been directed "to understand and be able to update ASAP". Unfortunately, I am a fairly "green" programmer and have run into this error. I think it is tied to the use of threed32.ocx. Any ideas or direction?
 
Rdeleon - the SSPanel part sounds familiar - I think they are using a downloaded custom control that requires a license ... which you don't have installed on your PC. Ask them if they have any installation files for you to execute.

Let me know if you come right.
 
There is an installation file available (I have not executed it yet), but if I am suppose to update this program, how do I reverse engineer the installation file to understand what files I need to include in the future to get the program to compile again?

As I mentioned before, I'm relatively new to VB so the more explanation you can provide, the better.
 
If its the same program I'm thinking of (pls correct me if I'm wrong) - it's something called a spreader bar/page or something on those lines. Quite a nice little grid layout with a lot of added functionality. I don't really know too much about the files included (we worked on machines where it was already installed). I think there is a help file or text file with the installation but I could be wrong.

Just a small tip - if you can possibly write your own component to replace this one - that is always a better situation. you can support your own code (obviously) if anything goes wrong and you are not bound by any license agreements. Its not that difficult to write your own components ;-)

Best of luck with this and keep me posted!
 
On the VB6 CD you can find the answer in \Common\Tools\VB\controls
Quote
This directory contains all of the ActiveX Controls that shipped with Visual
Basic 4.0/5.0 Professional and Enterprise Editions, which are no longer shipping
with Visual Basic 6.0.

AniBtn32.ocx
Gauge32.ocx
Graph32.ocx
Gsw32.EXE
Gswdll32.DLL
Grid32.ocx
KeySta32.ocx
MSOutl32.ocx
Spin32.ocx
Threed32.ocx
MSChart.ocx

The \Tools\Controls\BiDi directory contains a Bi-directional version of
Grid32.Ocx.

If you have Visual Basic 5.0 Professional or Enterprise Editions installed on
your machine, you should already have these ActiveX controls available to you in
Visual Basic 6.0.

Graph32.ocx has been updated to work properly in Visual Basic 6.0 and it
requires two additional support files: gsw32.exe and gswdll32.dll. You must
place the three files together in the \Windows\System directory or the control
will not function properly.

If you do not have these controls and wish to use these in Visual Basic 6.0, you
can install them by:

1. Copy all of the files in this directory to your \WINDOWS\SYSTEM directory.

2. Register the controls by either Browsing to them in Visual Basic itself, or
manually register them using RegSvr32.Exe. RegSvr32.EXE can be found in the
\Tools\RegistrationUtilities directory. The command line is:

regsvr32.exe grid32.ocx

3. Register the design time licenses for the controls. To do this, merge the
vbctrls.reg file found in this directory into your registry. You can merge this
file into your registry using RegEdit.Exe (Win95 or WinNT4) or RegEd32.Exe
(WinNT3.51):

regedit vbctrls.reg (or other reg files associated with the controls)
 
thanks for the information. I think the problem is that the previous programmer used a 3rd party ocx and when I tried to open the project in design mode, the ocx controls were converted to pictureboxes (?). Does this sound familiar? A programmer friend of mine mentioned that I needed to get a design license from the 3rd party ocx vendor in order to design with the custom controls.

I'm assuming that if I contact the vendor they will have instructions as to what I need to buy and/or install. Any insight on this?

 
Yup - VB tends to convert controls that it can't interpret to pictureboxes.

Unfortunately you do need the design license :-( (again, if its the same control I'm thinking of) - give the vendor a shout and see what happens
 
I just wanted to say on the VisStudio 6 enterprise you'll find all the controls in \COMMON\TOOLS\VB\CONTROLS on the third CDROM.

Note just copy all these files to the system directory and double click the included file VBCTRLS.REG after you copy it with the others to the system directory. This registers all of them at once.

Buck :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top