I was in the same situation and I went with:
- Converted my entire application to Access2007
Use some access2007 features where they make sense (example the ribbon,
datasheet improvements)
- Use SageKey for the install
It worked out well.
Here's an article on my experience with sagekey:
http://www.rptsoftware.com/help/micr...ty/sagekey.asp
I think Access2007 requires XP SP3 or higher.
Basically it's how difficult is the conversion that affects your decision,
but given that you are buying some
pricey tools like sagekey I vote for the big conversion.
I do not think any other installers get you past the issue that different
versions of office do not work well together.
Sagekey at least does that ok.
My two cents,
--
Mark Andrews
RPT Software
http://www.rptsoftware.com
http://www.donationmanagementsoftware.com
"BobbyBob" <(E-Mail Removed)> wrote in message
news:5AAD627C-5AA8-4EB5-91C5-(E-Mail Removed)...
> Thanks in advance to anybody that can offer an opinion or advice.
>
> Scenario
> I have developed an application using Access 2000 that I intend to make
> available for users to download from a web site along with Access 2007
> Runtime if required. (Users could have any version of access on their
> machines or might not have any version of access.) Users could be using
> any
> version of Windows.
>
> Dilemma
> In an earlier post I was advised to use Sagekey for the installation to
> avoid version conflict problems with Access 2007 Runtime and to simplify
> the
> installation. Unfortunately, Sagekey no longer supports Access 2000.
>
> Questions
> 1) Would I be better to persevere with Access 2000 and use another
> installer
> (perhaps INNO?) or change to Access 2003 (I know have a copy somewhere) so
> that I could use Sagekey?
> 2) Could I use Access 2003(for future application development) and Access
> 2000(for further development of other exiting applications that are being
> used by existing clients with Access2000) on my machine without any
> problems?
>
> Would be so grateful for some advice and guidance.
>