×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

setup.exe calls a MSI

setup.exe calls a MSI

setup.exe calls a MSI

(OP)
hello,
  I am repackaging an application in which the application setup.exe calls a MSI which installs Access on the machine.

After installing the repackaged application when I double click the .mdb file nothing happens. It does not work even if I use "open with" msaccess.exe.

The mdb file opens when I go to Start Menu-> Run and type msaccess path\file.mdb.

I checked the file associations which seem to be correct in the wise.

Plz help    

RE: setup.exe calls a MSI

It sounds to me like your Access installation isnt working properly.

First of all, you should not repackage a setup.exe that unwraps an msi.
Clear your Temp-folder, start the setup.exe.
On the first welcome screen or whatever it comes up with, go to your Temp-folder to see if the msi has been unpacked from the setup.exe.
If it has, copy it to a different location and cancel the setup.exe.
Now run your msi or create transforms to it or whatever.

Please revert with your findings.


RE: setup.exe calls a MSI

(OP)
Actually they r 2 diff programs. One is TeamRisk whoes installation calls the MSI of Access 2000 runtime. I have made an MSI of TeamRisk which in turn calls the  MSI of access(nested installations).

RE: setup.exe calls a MSI

Access 2000 runtime is a pain in the arse.

Try this.

Manually install Access 200x runtime on your build pc. Do the reboot thing.

Now start a Setup Capture, and capture your actual application. It should realise that Access2k is already installed and just skip over it.

I've had to do this for a few apps here because our SOE includes Access2002 which I really don't want to be writing over with a runtime version.

Try installing Access or the runtime first b4 u install your proprietry app.

Cheers

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close