Link to home
Create AccountLog in
Avatar of bgdw
bgdw

asked on

VB6 application is not running on Vista

Our VB6 application is not running on Vista.  We believe we've localized the problem to 'DBGrid32.ocx'   Microsoft claims they support 'DBGrid32.ocx' in Vista but do not install it.  We are installing DBGrid32.OCX version 5.1.81.4 (514 MB, 6/26/1998).

Our VB6 environment has service pack 6.  

Comcat is the only dependency listed in the DBGrid32.DEP file, and it is installed.

Please help!
Avatar of Anthony2000
Anthony2000
Flag of United States of America image

Have you created a simple app that only contains DBGrid32.ocx and tried that. This way you can be 100% sure it is causing your problem.

I am assuming that you have already tried unregistering and re-registering it too.
Avatar of bgdw
bgdw

ASKER

Anthony2000,

Thanks for getting back to me.

 When running a VB6 application with only a form hosting DBGrid, I got the following error message:
 
"Component 'DBGrid32.ocx' or one of its dependencies is not correctly registered: a file is missing or invalid"

We've tried unregistering and re-registering, same deal.
 
Have you tried unregistering comcat and re-registering it? And make sure they are properly matched (version wise). I don't know what versions are compatible. You may have to do some searching on Microsoft's website.
SOLUTION
Avatar of graye
graye
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of bgdw

ASKER

Thanks to both of you.

I've tried the un-register / register comcat.dll - No luck.

We are going to install the VB Development envirnment on the Vista machine next.  I'll let you know who we do.
Loading the dev environment should help solve your problem. If for some reason it doesn't. I had a similar problem and I used Filemon from Microsoft to find out what was going on.

http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx
Avatar of bgdw

ASKER

I just ran the program using the Windows Vista "Start application in Compatibility Mode."  It ran like a champ.  Does this give you guys any clues?

Thanks,
Yes, that jogs my memory. I think it could be related to something in how the registry works in Vista rather than in XP and prior versions.

I thought I read that each user has a separate set of some keys in the registry. So, when you modify the file associations for .bmp, you are probably doing it for the admin. Then when you run the program you are running it as a different user who just happens to have a different association then the admin user.

Okay, I have to admit, I am guessing alittle as well. I could be 100% wrong about this.
Avatar of bgdw

ASKER

Let me update you.

It ran perfectly in Start application in "Compatibility Mode."  Before I clicked "Finish" to set the program to perminent "Compatibility Mode" I clicked cancel.  So the app was not set to "Compatibility Mode."  

Now when I run the app, it runs perfectly.  I believe it does have something to do with being the admin.  Now that the app ran successfully, the dll and OCX both got registered correclty and now run.  Does that jive with what you are thinking?

If so, how do I setup the installation to do whatever happened in the "Compatibility Mode?"  Insist that the user be the administrator?  That does seem like a good solution.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account