installing access runtime changes default program to open mdb's

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a runtime version of my application which I want to install on users machines, some of whom have already got another version of access on their machine. When my runtime version is installed it automatically becomes the default version to open .mdb databases. How can I prevent this from happening?? Maybe I am wrong to distribute it as .mdb should I convert it to .mde first?? I suppose this will make it the defult for .mde then, I don't want that either. How can I prevent my access version (2003) automatically changing any default?? Is it something I do wrong in the packaging wizard?? Thanks to anyone who can help.
 
Nasos said:
I have a runtime version of my application which I want to install on
Click to expand...
users machines, some of whom have already got another version of access on
their machine. When my runtime version is installed it automatically
becomes the default version to open .mdb databases. How can I prevent this
from happening?? Maybe I am wrong to distribute it as .mdb should I convert
it to .mde first?? I suppose this will make it the defult for .mde then, I
don't want that either. How can I prevent my access version (2003)
automatically changing any default?? Is it something I do wrong in the
packaging wizard?? Thanks to anyone who can help.

Using the scripts from SageKey and a third party installer like Wise or
InstallShield it is reported that you can create a Runtime installation
that has no affect on the existing system as you are seeing. I don't think
this can be easily accomplished using the installer that comes with the
Office Developer's tools.

If you don't want to dish out the bucks for SageKey and an installer it is
generally recommended that you include multiple versions of your app for
distribution and only install the Runtime on PCs that have NO version of
Access already installed. For those that do you simply install the
application file in the version already on the machine.
 
-----Original Message-----
I have a runtime version of my application which I want
Click to expand...
to install on users machines, some of whom have already
got another version of access on their machine. When my
runtime version is installed it automatically becomes the
default version to open .mdb databases. How can I prevent
this from happening?? Maybe I am wrong to distribute it
as .mdb should I convert it to .mde first?? I suppose this
will make it the defult for .mde then, I don't want that
either. How can I prevent my access version (2003)
automatically changing any default?? Is it something I do
wrong in the packaging wizard?? Thanks to anyone who can
help.
.
The runtime was made purley for machines that don't have
Click to expand...
Access on them. The only way around this is:
(1) Remove Access from the machine, leave all the other
Office programs there, and then run your access setup.
(2) Convert the Database to version on the PC.

Leon
 
Rick Brandt said:
If you don't want to dish out the bucks for SageKey and an installer it is
generally recommended that you include multiple versions of your app for
distribution and only install the Runtime on PCs that have NO version of
Access already installed. For those that do you simply install the
application file in the version already on the machine.
Click to expand...

Setup Switcher is designed to install either Access97, Access2000 or
newer related runtimes depending on what's already on the recipients
system. See http://www.granite.ab.ca/access/setupswitcher.htm.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top