Hello, Alex
Related to this question - I have an app using Access XP that is distributed
with a setup option 'complete' or 'database only'. Complete is for users
without Access installed. Problem is, if the user has a newer version of
Access (2003 or 2007), the setup will not run the database-only option. It
is apparently looking for Access XP and only that version will do. How can I
change it to install just the mde if there is a later full version of Access?
This was created, BTW, with the setup wizard in XP developer tools.
"Alex Dybenko" wrote:
> Hi,
> best approach - is to install runtime only when access is not installed.
> Unfortunately you can't check this with PDW, so you have to ask customers if
> they have any access version installed. with SageKey scripts and
> installation system like Wise you can check if user has access installed (by
> querying registry keys) and then install runtime when necessary
>
> benefit to distribute in Access 2000 format - is that it can run on any
> access version from 2000
>
> --
> Best regards,
> ___________
> Alex Dybenko (MVP)
> http://alexdyb.blogspot.com
> http://www.PointLtd.com
>
>
> "glynng" <(E-Mail Removed)> wrote in message
> news:2C87BEDC-4BDC-41E3-B53C-(E-Mail Removed)...
> > I'm new to this and somewhat concerned about deployment of Access 2002
> > application using packaging wizard. Simple app, nothing fancy.
> >
> > How vulnerable will I be to customers installing the runtime on PC's with
> > different Access versions, older or newer?
> >
> > Is it necessary to restrict to certain versions, i.e. Access 2000 or
> > greater..
> >
> > Is there a benefit to distribute in Access 2000 format?
> >
> > Is is necessary to use an installation product like SageKey instead of
> > Packaging Wizard?
> >
> > Thanks in advance
> >
> >
>
>
Similar Threads
