HELP! Can't get compiled App to work on other machines!REALLY!!!

[jamus]

I am having trouble getting my compiled projects to work on other machines. I've packaged and deployed the project a number of different ways and I'm wondering if there's something I'm missing. I'm pretty new to this whole process. I'm just trying to compile and distribute a demo version of something. It's very simple with very little functionality. (just pop-up menus and tab pages) It's just meant to be a graphic representation of what I need some programmers at my company to do.
PLEASE HELP ME FAST!!!!! BIG HURRY!!!!
THANKS
Jamus

 

[binky]

I had a lot of problems with this very thing. I had to download Service Pack 4 to fix my problems.

Without knowing what kinds of things are in you program I can't really say for certain if this will help you for sure or not. BUT, it can't hurt!

Hope this helps!
Ken

 

[jmarler]

First off, what kind of error are you getting when you try to run the compiled code on the other machines? - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)

 

[VBVines]

I don't know what problems exactly you are having but it seems that whenever I deploy anything the three things I always do that seem to cover a variety of issues is make sure that on the client box you install, Dcom98, Mdac 2.5, and on your developement box install the fourth service pack for Visual Studio. aspvbwannab

 

[jamus]

the message I'm getting is something like:
"unable to create installation log"

Actually, just for kicks I burned the whole project on to a CD ALONG WITH the actual application (VB 6.0) and when I opened the project on another computer, the install worked. I could then take out the disk and it worked just fine after that.
J.

 

[jmarler]

So, your plan is to install VB6 on every machine that needs to run your code? - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)

 

[jamus]

Obviously not, but I justed wanted to see if it would work. I had to get it working somehow, just temporarily. Besides, It didn't INSTALL VB6. I guess the install process was missing some things that it could just get from VB6 on the disk at setup time and then it was fine.