[RESOLVED] My Application doesn't work on other PC's...MOMMEEE

[Avatarp]

I have been trying to get my application installed on another PC. I understand that I have to include files for MDAC, OLE, DAO, ADO, among others for which ever version of Windows. I downloaded VB_DCOM_MDAC_JET_AutoSetup.exe to handle this and included this in my inno script to run. This file auto-detects which OS it is installing the required files for. however I have included many of these files in my script as well.

The problem is not that my program won't run. It is that as soon as I do something to query the Database it freezes. This doesnt happen on my PC! I even decided to hardcode the location of the DB just to test wether it is my DB location. It isn't. So it must have something to do with my install

I would really appreciate any help from you guys and gals.

Thanks in advance.

[Avatarp]

Here is my inno script


; Script generated by the Inno Setup Script Wizard.


[Files]
; START VISUAL BASIC

[Run]
Filename: "{tmp}\VB_DCOM_MDAC_JET_AutoSetup.exe"; Parameters: /NORESTART /VERYSILENT WorkingDir: {tmp}; MinVersion: 4.0,4.0
Filename: "{app}\HomeSalonOrganizer_NoReports.exe"; Description: "{cm:LaunchProgram,Home Salon Organizer (No Reports)}"; Flags: nowait postinstall skipifsilent

[kleinma]

what is VB_DCOM_MDAC_JET_AutoSetup.exe and where did you get it from?

[Avatarp]

I got it from here


http://www.**********.com/support.html

[kleinma]

well you may want to try to see if Randem (he is a forum member) has any insight or has seen the issue before, as that is his site.

[mesathinks2002]

Not sure if this is any help...

but when I built my app for MySQL I used one build and when I went to install it they had gone from something like 4.0002.001 to 4.0002.003 (made these numbers up but the change was about that small). It was just enough to freeze my app when I tried to run it and access an online database.

[randem]

Avatarp,

You have too many conflicting files in your script that can do harm to your installation. Try Running ********** (http://www.**********.com/**********.html) on your VBP file and then compare it to the script you created.

This will help you eliminate some of the files that you should not be deploying.

Let's start there...