The shortcut for the runtime app should already have the full path to
msaccess.exe /runtime somefile.mdb, so it should continue to load the
correct version.
In a runtime, you probably did not use calls to other Office libraries, so
they should not break. However, if you used MSGraph, Calendar control, etc,
you may find the references for these objects are broken when the newer
Office version replaces them.
If you end up using A2003 to work on the application, make sure you
decompile it under A2002 and release the final MDE from that version. Even
though they are file-compatible, the binaries are different, and the A2002
runtime will not work if you use an MDE created under A2003.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"WØCBF" <w0***@yahoo.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...
I have an Access application that was written in ver 2002. I have
distributed the application to our other offices using the Developers
Toolkit and installed a runtime version of Access. At that time no
other versions of Access was on their computer systems. Now, if Access
2003 (full version) is installed on each machine what will this cause
to the run time version of Access as well as the application. Is their
anyway to control the application so it will only run under the earlier
2002 run time version? The boss does not want to buy a copy of the 2003
Toolkit.
I could use whatever and appreciate help you can give.
Thanks
Chuck
