Access 97 under Win XP and/or Win 2003

[David]

Does anyone know whether Access 97 and Access 2000 can be
used under Microsoft XP or Windows 2003?
I've looked on the Microsoft web pages and have not found
a clear cut answer so far.

 

[Tony Toews]

Why not recommended to run apps on a server??

They can slow down the overall response time of the server. They can
load on rogue DLLs and cause troubles. They can require you to reboot
the system which you don't want to do during the day.

Chances of these kinds of problems are relatively low but still
possible.

We do it all the time. With Access its far to slow to pass
data back and forth to another machine.

There are things you can do here to improve performance but yup,
there's nothing like working on the server.

The three most common performance problems in Access 2000 are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Our apps require no user input.

Presumably you're doing this for reporting purposes then.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Joe Nesheim]

I successfully ran Access 97 on a computer having the
Windows XP operating system for several weeks ... until
someone else installed Office 2000 over the top of my
Access 97. Now I can not get it to run at all even though
it appears to re-install properly (after I removed Office
2000)

I believe Access 97 can work just fine on an Windows XP
machine.