J
Jetera
I have created an access 2000 runtime - will this work in a machine that has
Access 97- if I include the runtime file?
Access 97- if I include the runtime file?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Micah Chaney
Try it and find out, and let us know.
S
SJ
follow the advice in the knowledge base about installing multiple access
versions...
http://support.microsoft.com/kb/q241141/
ie, rename the hatten font and rename the msaccess.exe temporarily....
when you've got 2 versions on the machine you need to be specific in the
shortcut as to which msaccess.exe you want to fire up. 97 or 2k Don't
install into the same directory....
If you double click an mde or mdb in explorer the "last fired" version will
fire. Access self registers its version in the registry each time you
start it up. You'll see what I mean...
its work just fine, you can put XP and 2003 on there as well if you wanted.
Runtime or full version. Some things don't go so well under runtime but
its usually pretty good.
versions...
http://support.microsoft.com/kb/q241141/
ie, rename the hatten font and rename the msaccess.exe temporarily....
when you've got 2 versions on the machine you need to be specific in the
shortcut as to which msaccess.exe you want to fire up. 97 or 2k Don't
install into the same directory....
If you double click an mde or mdb in explorer the "last fired" version will
fire. Access self registers its version in the registry each time you
start it up. You'll see what I mean...
its work just fine, you can put XP and 2003 on there as well if you wanted.
Runtime or full version. Some things don't go so well under runtime but
its usually pretty good.
C
ChristyWarner
Hi,
Does anyone know how to handle this from WITHIN the Package Wizard
of Access 2003? It seems like when I install my app on another
machine using the setup.exe, it still looks for the default Access version
instead of the Access 2003 runtime version I included in my Wizard setup
package. Once I manually change the shortcut target, it works OK,
but it seems to populate this field w/ the version of Access that the user
already has on their machine.
Confused and Frustrated,
Christy.
Does anyone know how to handle this from WITHIN the Package Wizard
of Access 2003? It seems like when I install my app on another
machine using the setup.exe, it still looks for the default Access version
instead of the Access 2003 runtime version I included in my Wizard setup
package. Once I manually change the shortcut target, it works OK,
but it seems to populate this field w/ the version of Access that the user
already has on their machine.
Confused and Frustrated,
Christy.
T
Tony Toews
ChristyWarner said:Does anyone know how to handle this from WITHIN the Package Wizard
of Access 2003? It seems like when I install my app on another
machine using the setup.exe, it still looks for the default Access version
instead of the Access 2003 runtime version I included in my Wizard setup
package. Once I manually change the shortcut target, it works OK,
but it seems to populate this field w/ the version of Access that the user
already has on their machine.
This is standard behavior of all of the runtimes.
Likely the best solution is a third party install routine such as the
one by Sagekey.
Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.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