ODE 97 Runtime

  • Thread starter Thread starter Winnetou
  • Start date Start date
W

Winnetou

I have an old version of MS Office 97 Developer Edition Tools (ODE).
The version was designed for Windows 95/NT. I assume therefore that
the runtime version will only generate code suitable for these OS.

Questions: 1. What are the implications/side effects if I were to load
such a runtime file on a Windows 98/ME/2K etc. machine? 2. Would such
a runtime app. play havoc on the registry settings and delete file
association relationships? 3. Is there such a thing as an ODE version
for Windows 98? 4. What is the best approach: a. create a runtime
version for each OS (98/ME/2K..) or b. have a basic version, based -
say - on ODE 97 & Windows 98, that could somewhat be shielded from the
user's current Access version and would therefore not interfere with
the registry settings?

I have not yet tested this on my 98/ME machines for fear of deleting
registry and/or file association settings. Please advise.

Thanks for your feedback.

Mark
 
ODE97 installs work OK on Win98, but haven't tried them on Win2000/XP. My
experience with multiple versions of Access recommends that you install the
most recent/standard version first, then install the earlier versions in
separate directories.
-Ed
 
Ed,

Thanks for your reply. Based on what I read about the run-time size of
Access 2k and up, I am inclined to only use A97. However, I am aware
of the registry and table association pitfalls that arise when you
install a run-time file in an existing higher Access environment.

So my questions are: 1. Do you gear the app. to each Access version
and ask the user to choose the appropriate version or 2. Do you create
a single run-time version in A97 and download this onto the target
machine (using sthg. like SageKey to avoid overlapping)?

Thanks for your feedback.

Mark
 
Acc 97 Runtime will install just fine on 2000/XP
machines. The problem will come in where the user already
has Access 2000, XP, or 2003 installed on their computer.
You should have a seperate Access 2000 version to run in
that case.


Chris
 
Back
Top