windows 2000 and access 97

  • Thread starter Thread starter HOlly
  • Start date Start date
H

HOlly

Can anyone tell me if there are current issues with access
97 on w2k? I have some access 97 databases which run fine
on NT but on 2k i get constant "Invalid Database Object
Reference" errors when I close tables for example. Also
when i go to Import data, I don't get all the files of
type listed that I get on NT - I have installed all the
options in add/remove in office 97 so it shouldn't be
missing anything. Anyone had the same problems?
Thanks
Holly
 
I have found Win2K to be the most stable OS that Microsoft has ever
produced. I currently use it on several of my machines and on most of my
servers.

From the messages that you are receiving, it appears that you may have a
corruption issue. Have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Arvin
I very much doubt it is an access corruption as it is
happening to ANY database (approx 20 in total) I try
through the win2k machine (w2k server) and it doesn't
happen when i use the databases on any machine running
NT. It must be something to do with the 2k Operating
system and these files.
I agree 2k is a very stable OS, don't think thats really
an issue here though..
I have checked your URL out and couldn't find the error
message I get on there when looking through the database
corruption messages.
 
Just to let you know, I have now resolved this issue, it
was to do with users sharing the system.mdw file. I have
changed the way the app runs so it looks for a unique
system.mdw file for each user logged onto it (it is a
terminal server so more than one person was using access
at a time).
 
Holly said:
Just to let you know, I have now resolved this issue, it
was to do with users sharing the system.mdw file. I have
changed the way the app runs so it looks for a unique
system.mdw file for each user logged onto it (it is a
terminal server so more than one person was using access
at a time).
Click to expand...

Can you elaborate? I haven't had this issue before, and I have had multiple
users connected to a secure system.mdw (in fact, that has been the best way
to do it).

I have some, but not much, experience running Terminal Services. A Terminal
Server typically functions with many instances of one copy of the file, so
I'd like to understand why (and how) you created separate system.mdw's on
the server that connect to the single file. Was there a KB article on this?
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Back
Top