ADO and Office 95

  • Thread starter Thread starter Ilan
  • Start date Start date
I

Ilan

I have Office Developer 2000, which enables me to write projects and ship
them with an Access database to end users which have Standard Editions of
Office.

If I write code which includes ADO, will the program still work on an end
user machine, if the end user has a pre ADO version of Office, such asOffice
95?

Many thanks for your reply.


Ilan
 
If you're writing an application using Access 2000, your users must have
Access 2000 installed to run it. A user with only Office 95 would not be
able to use your application.

However, Office Developer allows you to ship a royalty-free run-time version
of Access that your users will be able to install so that they can use the
Access 2000 application. The run-time is actually the same executable as
you're using (severely limited in what it can do by literally hundreds of
registry entries), so it will install all that's necessary for Access 2000
to run.

Note that there can be problems install the runtime on machines that already
have another version of Access installed. You may want to look into 3rd
party tools for this. You can get more advice in
microsoft.public.access.devtoolkits (or
microsoft.public.developers.toolkitode)
 
A package created with the Office Developer Setup and Deployment Wizard will
include the ADO files, and attempt to install them if they are not present.
The PC is quite likely to have some version of ADO installed, as many other
applications, not just Office, will install it if it is not present, but
you'll need to include the ADO files in your package as the version
installed on the PC may not match the version required by your application.
 
Thank you. Basically, you are assuring me that in I can write my application
and ship it, but I should then expect it not to work ;-) not without more
effort at least.

And than you for the references for the more specific newsgroups on this
subject.


Thanks


Ilan
 
You may want to include MDAC_TYP.exe file (download it from Microsoft
website) in your package. I always do it in Visual Basic 6 projects to avoid
a common runtime error, but I've never had this problem with MS-Access.

[]
Luiz Cláudio C. V. Rocha
São Paulo-Brazil
 
There is more work involved in deploying a runtime installation than in
simply deploying an Access application to a PC that has the required version
of Access installed, that's for sure.

I would consider using DAO instead of ADO in this scenario - there are fewer
different versions to worry about.

Create the setup and deployment package on a clean install of the earliest
version of Windows you intend to support. If any users are running Windows
ME, you may need to create two packages. In our experience, an Access 2000
package created on a clean install of the original release of Windows 98
(not 98 SE) installed successfully on all later versions of Windows except
Windows ME - we had to create a separate package on a Windows ME PC to
install on target PCs running Windows ME.

Also check out the SageKey utilities at www.sagekey.com
 
Back
Top