"Object variable is not set" error on one machine only!

[tatochka]

I can't solve this problem for a few days now. I packaged my application and test it installing on a few different machines. Only one Windows 95 machine gives me the error message" Object variable or with block variable is not set" when running application. There was no error during installation of application. Other Windows95 machine work just fine for me with no messages. I checked if all *.dll and *.ocx files mentioned in references and components of the project are in my Support directory (of installation). And they all are. I could not figure out what the problem is and decided to install VB6 on this PC so I could debug application.

Guess what?! As soon as I installed VB, application ran just fine there was not any error message anymore. There is obviously something that VB installed on that machine (and what other machines have installed already) and what I am missing in my installation package. Any idea what can it be? Please help! I have to solve this, because my users will have the same problem I am sure and I have to know how to fix it.

 

[olichap]

In your installation package you might check whether there are Merge Modules (MSM files) for some of your dll's. I recently realized for a new app I was putting dll's from my 2000 machine into my install package. Originally this was just done out of haste; I was only running it on a lab/test pc. When I started distributing it around my office problems surfaced. Once the MSM's were used instead, no problems with the install were evident.

If you use the Visual Installer that is part of Visual Interdev it will tell you when an MSM exists.

 

[Brewman76]

Thinking back to a problem I had with a VB app on Windows 95... Make sure DCOM98 is installed on the Windows 95 machine. YOu should find a small install pkg for it on any Windows 98 machine.

 

[tatochka]

Just wanted to add something...
The package was created with VB6 package and deployment Wizard. I downloaded the latest DCOM95 on this test machine. Still have the "Object variable ... not set" error message . (I uninstalled VB to get the message back). I ran "Dependency Walker" utility for VB *.exe file on my development (Windows98) machine to see all the dependency files. They all are installed on test Windows95 machine. I don't know what else to do. Please, help!!

 

[tatochka]

In case somebody is interested... I was chasing the missing dll for a long time and finaly, using "Picture taker" software, got a list of all dlls that VB installs. For some reason the dll that I needed to add to my installation package was vb5db.dll. This dll was not in dependency list of my project and was not in setup.lst file.

 

[chiph]

Interesting. I wonder what needs that DLL in a VB6 project?
I bet installing the latest MDAC would solve that.

Chip H.

 

[jonscott8]

See

http://support.microsoft.com/support/kb/articles/Q241/2/81.asp

Jon Hawkins