I have an old Visual Basic 3 program I'd like to upgrade but when I attempted to use the upgrade wizard, it complained about being unable to convert TABBED.VBX and changed it to PictureBox. I noticed that I can add the Tabbed Dialog component (TABCTL32.OCX?) to the toolbar in VB6, but it's not there initially. Is there a way to make it included by default and would that allow it to convert, or am I stuck with doing a massive rewrite of that component in VB6?
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Upgrading VB3 program with Tabbed dialog to VB6
- Thread starter weberm
- Start date
>am I stuck with doing a massive rewrite of that component in VB6?
I refer you to the answers you've been given in thread221-1693439
More specifically for this instance:
TABBED.VBX is not a Microsoft control, and was never supplied with VB3, as far as I can recall. It was a third party control - so Microsoft would have no reason or obligation to ever have provided any facility to convert it to an equivalet OCX.
>Is there a way to make it included by default
Pretty much. You basically need to create a project (empty) with all the add-ins and other componetrs you want loaded by default (in you case TABCTL.OCX), then save the project to your templates folder (typically found here: C:\Program Files\Microsoft Visual Studio\Vb98\Template\Projects). Make sure all the files making up the project have meaningful names that don't conflict (and thus overwrite) any of the files already in that folder.
Next time you do "File/New Project" your template will appear as one of the options.
>would that allow it to convert
No
>stuck with doing a massive rewrite
Afraid so
I refer you to the answers you've been given in thread221-1693439
More specifically for this instance:
TABBED.VBX is not a Microsoft control, and was never supplied with VB3, as far as I can recall. It was a third party control - so Microsoft would have no reason or obligation to ever have provided any facility to convert it to an equivalet OCX.
>Is there a way to make it included by default
Pretty much. You basically need to create a project (empty) with all the add-ins and other componetrs you want loaded by default (in you case TABCTL.OCX), then save the project to your templates folder (typically found here: C:\Program Files\Microsoft Visual Studio\Vb98\Template\Projects). Make sure all the files making up the project have meaningful names that don't conflict (and thus overwrite) any of the files already in that folder.
Next time you do "File/New Project" your template will appear as one of the options.
>would that allow it to convert
No
>stuck with doing a massive rewrite
Afraid so
- Thread starter
- #3
I fetched a copy of Professional VB3 and VB4 http://www.ojodepez-fanzine.net/network/qbdl/]online[/url] and it had no trouble with TABBED.VBX in VB3. VB4 came with Sheridan Tabbed Dialog Control (TABCTL32.OCX), but I seem unable to import the VB3 version. I created a new tabbed dialog in VB4 and VB6 had no problems importing it intact, so it appears I will only need to rewrite it once. ![[wiggle]](/data/assets/smilies/wiggle.gif "[wiggle] [wiggle]")
Now I need to clean up the VB3 code so the objects have more meaningful names than "txt15" and "command21".
Now I need to clean up the VB3 code so the objects have more meaningful names than "txt15" and "command21".
- Status
Similar threads
