br****@rimesrv.net wrote:
I have an Access 97 app and the ADT and am considering selling it to
the public.
Is this viable? What issues might I have?
I also have Access 2000 and could use that if it would be better. I
don't have the "ADT" for 2000. Is it called ODE or ODT? Can you
still buy that?
Would there be any advantage in moving up to and distributing using
Access 2002 or 2003?
I'm not up on .NET technology.
Appreciate any advice.
As long as you don't require any of the features in the newer versions Access 97
will provide an app that is smaller, faster and which will run on more PCs.
Since there is no reason to use more than one runtime then that is what I would
use.
Most of the "issues" with the runtime involve installing it on PCs where a
version of Access already exists. This should be avoided whenever possible.
The ultimate installation package for your app would be one that installs only
the application and support files of the proper version on PCs that already have
Access installed and which includes the runtime only on PCs that don't have any
version of Access already installed. This sounds daunting, but since Access
2002 and 2003 can both run Access 2000 files just fine you really only need two
file versions, one in Access 97 and one in Access 2000. This means you have
three scenarios that you can cover pretty easily...
* Target PC has no version of Access
(install 97 runtime and all support files)
* Target PC has Access 97
(install Access 97 file and all support files)
* Target PC has Access 2000 or higher
(install Access 2000 file and all support files)
The ADT for Access 97 cannot build such an intelligent installer, but it can be
configured to install as many MDBs in as many versions as you want to include as
well as the 97 runtime and all of these can be configured as optional
components. This would at least allow a user that is knowledgable about his
system to only install the components that are appropriate for his situation.
If you obtain more complex installer packages like Wise, InstallShield, etc.,
then it might be possible to build an installer that requires less of the person
running the install, but you would need to investigate that to see what the
exact capabilities of those programs are.
Another way to go is to build a runtime install package that uses the scripts
that can be purchased from Sagekey. These scripts make the runtime installation
of your app so that they are much more independent. By that I mean that they
don't "mess with" any other versions of Access that might or might not exist on
the target PC. I have never used these, but everything I have ever read about
them indicates that they work as advertised.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com