Hi, Vincent.
I have an app that was built to run in runtime 2000 but is being ran on 2002.
My question is are there any know complication if i were to upgrade to
2003?
Probably not, but it depends upon the configuration. Do you plan to install
and run all of these on the same computer? The database application built
for a runtime version must be more robust than the application built for the
retail version, so the problem isn't with this particular database
application. However, if it's run with a retail version of Access, then the
built-in toolbars and shortcut menus will be present, so if the database
developer created custom toolbars and menus for the application, there will
be some redundancy.
It sounds like the Access 2K version is the runtime version. Are the rest
of the versions of Access the runtime version or the retail version? Access
2003 will run database applications built in Access 2000 and 2002, so it's
probably best to remove the earlier versions and just keep the latest
version if all of them are the runtime, since no database development work
can be done with the runtime version. However, if any version is a retail
version, then I'd recommend keeping it, too.
For whichever versions you keep, make sure that you have installed all of
the service packs for each version of Access, Jet and MDAC. (You may not
want to install MS Office XP SP-3 though, because it introduced a bunch of
bugs for Access 2002.)
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
Vincent said:
I have an app that was built to run in runtime 2000 but is being ran on 2002.
My question is are there any know complication if i were to upgrade to
2003?
