Application Installation Dilemma

[BobbyBob]

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.

 

[John W. Vinson]

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?

I'd go to 2003. It fixed a LOT of bugs and other problems with 2000.

 

[BobbyBob]

Thanks John.

Any thoughts on question number 2?

 

[John W. Vinson]

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?

You won't be able to take advantage of the new features (split forms, etc.)
that exist only in 2007, but both 2007 and 2010 can use 2000 format databases
as is without difficulty.

 

[Mark Andrews]

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/microsoft_access_thirdparty/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,

 

[BobbyBob]

Thanks John

Upgrading to 2007 is not an option at this time. Upgrade would be to 2003.
That said, I understand that A2000 files on my machine will work with A2003.
My concern is this: I have a number of clients that I’ve done apps for,
which use A2000. I presume that if these apps need developing in the future,
I will need to do this using A2000 on my machine. In this case will A2000
and A2003 co-exist on my machine without causing me any problems?

 

[John Spencer]

Yes, you can have 2000 and 2003 on your computer at the same time without
conflicts. I currently have Access 97, Access 2000, and Access 2003 running
on the same computer. I do have Access 2007 on a separate computer, but none
of my customers has yet upgraded past 2003.

You can develop 2000 databases in 2003 and then test them in 2000 to make sure
that you haven't used any of the 2003 functionality that does not exist in 2000.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County