Make sure another VB app wasn't run before yours. If the other app uses an
older version of Grid.VBX than yours does you'll get the error because the
older one with the same name is already in memory. You also need to look into
the order that Windows will look for the VBX. They may have an older version
somewhere in their path. You'll probably find if you shut off the other
system and start it up again (making sure that no VB app is being launched in
their Startup Group) and then run your app (making sure you have the newer
Grid.VBX in the apps directory) you won't have the problem.
_/_/_/_/_/_/_/_/
_/ _/ Systems Developer | Just an ArmaDELLo
_/ _/ _/ Dell Computer Corp. | trying to get across
_/_/_/ohn _/arr ta...@ccmail.us.dell.com | the Information Highway
The only thing I can think of that the machine you installed your application
on has an older version of GRID.VBX in the Windows system directory and you
copied the GRID.VBX to the application directory.
VB searches the windows-system directory before the application-directory
when looking for VBX'es. If this is the case, simply copy your version of
GRID.VBX to the Windows-system directory.
Hope this helps,
Arjen
--
Arjen Broeze Telephone: (+33)53-311950
ar...@shear.iaf.nl Address: Oostveenweg 55-13
7533 VR Enschede, NL
In particular, look for a "newer" grid.vbx from Visual C++. I hit this
problem a few months ago and wrote up the attached internal bug report on
this problem (and reported it to M/S). What I found was:
---------------------------------------------------------------------------
Installing Visual C++ V1.5 breaks Visual Basic's GRID.VBX. The version of
GRID.VBX in the VC++ kit is dated 11/23/93, and the version in the VB3 Pro
kit is dated 4/27/93. Visual Basic apps don't seem to like the newer vbx.
With the vbx from VC++ installed, applications that have been running
before the VC++ installation now give the following errors:
Columns must be one more than fixed columns value.
and sometimes:
The file c:\windows\system\grid.vbx is out of date. This program
requires a newer version.
Note that the first error message is wrong - columns must be greater than
the number of fixed columns, but not exactly one greater. And the second
message is certainly misleading based on the file dates.
---------------------------------------------------------------------------
John
----------------------------------------------------------------------
John F. Wood | Windows NT Technical Evangelist
Digital Equipment Corporation |
30 Porter Rd, LJO2-1/C10 | Internet : wo...@ljo.dec.com
Littleton, MA 01460 | AT&T : (508) 486-2577
----------------------------------------------------------------------
Disclaimer: Views expressed herein are my own and do not necessarily
reflect those of my employer.
Microsoft has the most rescent version for D\L on there BBS and at
ftp.microsoft.com, along with the other reccomendations make sure you
have there latest version.
I just obtained VBGRID.EXE dated 3-7-94 from Microsoft, you should be
able to find it at ftp.microsoft.com
There should be an updated called VBGRID.EXE in /Softlib/MSLFILES directory
in ftp.microsoft.com.
I had this same problem a while ago: Look into the /WINDOWS on that machine
and remove any .vbx's from there (they should all be in /WINDOWS/SYSTEM)
Hope this helps.
I had the same problem. In the windows/system directory grid.vbx had a
different date than all other vbx files.
Delete grid.vbx (or temporarily rename) and then reinstall custom
controls using the setup disks.
Hope it works.
Mukul Goel
Graduate Student
Civil Engineering
Texas A&M University
--
Jered Floyd
jjf...@vela.acs.oakland.edu
GAT d? -p+ c++++ l+ u++ e*@ m++ s/-- n--- h++ f? g- w++ t+++ r++
PGP Public key available by finger."