Packaging Wizard Access 2002 versus 2003

  • Thread starter Bill Sturdevant
  • Start date
B

Bill Sturdevant

I have been successfully creating packages with Access 2002 applications for
running on Office 2002. But, when I sent the package to a user with Office
(and Access) 2003, the setup package won't run because it insists it needs
Access 2002. How do I get around this one?
 
L

Larry Linson

I have been successfully creating
packages with Access 2002 appli-
cations for running on Office 2002.
But, when I sent the package to a
user with Office (and Access) 2003,
the setup package won't run because
it insists it needs Access 2002. How
do I get around this one?
Click to expand...

What kind of "packages" are you creating? When I use that term, I tend to be
talking about "packaging your application with runtime support".

Larry Linson
Microsoft Access MVP
 
B

Bill Sturdevant

I have not been including Access runtime because each of the users has Office
professional on their machine (and therefore has Access). The problem is the
organization is transitioning from 2002 to 2003 and I have held myself back
from 2003 to avoid creating install packages that will require 2003. I
figured that by staying with 2002, the 2003 people would be able to install
and run the 2002 package until everyone caught up and then I could switch to
2003.

I expected the install package to check for older versions of Access, but
not to prohibit versions that are higher thanthe one in which the package was
built.
 
Top