VBTools 4.0
Tech Support Questions

Q. I developed an application under Win3.1 with VB Tools v4.0. Everything has been working fine for about 6 months. About two months ago, I loaded the same application software on a WIN95 system that had previously been running Win3.1. Again, everything worked fine.

Recently I loaded a third machine with Win95 from scratch (ie: no Win31 or DOS present). Then I loaded the same app under Win95 using the same install program (created by Setup Wizard under Visual Basic v3.0). It installed fine.

However, when I go to run it I get a load error: 'Could Not Load Custom Control DLL WINDOWS\SYSTEM\MH3D200.VBX'. Is there a new Tools package that I should be buying that will run apps on both Win3.1 AND Win95? Will this cure the problem or is there a simpler work-around?

And, just out of curiosity, why did the app load okay on the first Win95 system (the upgraded one that previously had Win3.1) but not on the second (the Win95 one built from scratch). Both systems have 486-66/16Mb/1GB for components. Any suggestions?

A. There are a number of reasons why a VBTools VBX may not load on a particular machine. One of the first things to check for would be to make sure that the setup program installs the MhRun400.Dll (your first Win95 machine may have had the Dll already as our tools are pretty popular). There is VBTools 5 that was released about a month ago. This package was designed to be compatible with Win95 and VB4 and remain back compatible with Win31 and VB1. Although you may want to upgrade to VBTools 5 ($119) to get the latest in tools and compatibility, there is no know bug which would keep a VBTools 4 control from loading in Win95.

[TECH SUPPORT TOC]

[HOME] [TABLE OF CONTENTS] [SEARCH]