[RESOLVED] Compiled .exe won't run on other XP PCs?

[blueorange]

I had this problem, I had already install and registered the .ocx on the targeted PC's but the .exe that I compiled on my PC won't run on these PCs but only on my PC, when I run the .exe on other xp PC's it will just exit without prompting for any errors or missing ocx. Then I install Visual basic 6 on 1st XP PC and compiled the .exe there, the .exe runs on that PC and i tried it to copy and run on 2nd XP PC, it wouldn't run even if I installed the visual basic 6 on that 2nd PC. What I mean is, I have to install every PC's with visual basic and then compile the source code (build the .exe) on every machine. Even if I compiled the source code on 1 machine and copy the compiled exe to another pc (with visual basic installed and even all the ocx that I used), the .exe won't run. It would run only on the pc where it was compiled. How do I fix this problem. I tried a test by making test .exe's of all the ocx that I used and it runs fine on my pc and other pcs and these test exe's were compiled only once and on my PC. I already installed Service Pack 6 for visual basic and the same thing happen.. I used Adodb, does the problem is with adodb. I used mysql as my database and already installed these targeted PCs with MySQL connector for visual basic 6. Do any of you have any Idea, what's the cause of this problem? I used some .tlb in my program? is it the culprit? how do I install/register .tlb to a targeted PC? I used also dlls but they are mostly dlls of microsoft like GDI32.dll. Thanks for your help...BTW, my pc is Microsoft XP with Service Pack 3.

[LaVolpe]

TLBs do not need to be included with compiled exes, the TLBs are compiled into the exes. They do need to be included with uncompiled projects if you are sharing the raw source code.

Have you tried using VB's Package and Deployment wizard to create a setup.exe file for your project, then installing that -- I think this is your answer.

Why the app exits immediately without prompting for errors? No way for us to know for sure without the uncompiled application, but I am guessing that other dependencies do not exist on the other PC's, like the VB runtimes for example.

[Hack]

Have you tried using VB's Package and Deployment wizard to create a setup.exe file for your project, then installing that -- I think this is your answer.

I'm certain of it.

You can't just copy an exe from one PC to another. Your app will need to be bundled into a formal installation and setup package and the setup package shipped to all PCs that are appropriate.

[blueorange]

I'm certain of it.

You can't just copy an exe from one PC to another. Your app will need to be bundled into a formal installation and setup package and the setup package shipped to all PCs that are appropriate.

I tried using the VB's Package and Deployment wizard, but the setup cannot be installed on the targeted PC's because this msgbox will appear that

"Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files for you now.
You will need to restart Windows before you can run setup again. Click cancel to exit setup without updating system files."

I clicked OK and then the installer prompts to restart. After restarting the PC, I click the setup.exe again but this msgbox will still display and will do the same method as if updating the system files and prompt to restart the PC. I think it didn't update the files. Is there any other package deployment program other than the one included in VB that can do these things like look for dependency files in your program and create an installer?

[si_the_geek]

For solution(s) to that P&DW error, and links to alternatives, and documentation, see our Application Deployment FAQ.

[dicktracy007]

try packaging it with Inno Setup compiler and i did it by including the MSSCCPRJ file along with. Try and see

[RobDog888]

Thread Moved

[Nightwalker83]

I tried using the VB's Package and Deployment wizard, but the setup cannot be installed on the targeted PC's because this msgbox will appear that

"Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files for you now.
You will need to restart Windows before you can run setup again. Click cancel to exit setup without updating system files."

A possible solution to this problem is to allow the user to download the updates to the files themselves instead of packaging old versions of the files in the setup package.

[blueorange]

thank you every one for your replies. I found the cause why the .exe won't run on another pc, the culprit is the .manifest that I included in the .exe. I deleted the .manifest and the .exe now runs on other pcs.