Help please. In the mainframe world the
computer operator had total control and could just force someone off the
system. Do we have to take the network down?
Yes but you have to find out "who" on that mainframe system...would you not?
You can go into the server admin tools and view/see who has what file(s)
open...I would suggest doing that....
I want to stress EXTREME caution here in simply blowing out users that have
a file open. Remember, if you wring a word document, and you hit the re-set
key, then the changes in ram to that document are lost. With word, this not
such a big deal, however, with ms-access it can blow out the whole database,
and you be going back to yesterdays backup (you have one of
those...right!!!!).
For example, with all those disk frames in the mainframe...if we pull the
plug, then all that data in memory NEVER will get written back to disk.
You have to think of EACH copy of ms-access like a single instance of tat
mainframe (because EACH copy of ms-access has its OWN ram...and if that ram
is compromised due to a re-set...you can damage the file).
Read the following article VERY carefully as to why you can blow out..and
damage your file when you don't shut down each ms-access user correctly.
You can start reading at:
"Why a does JET file share corrupt when the connection breaks?"
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html
I just want to give you a conceptual understanding that in a file share,
parts of the file actually reside on EACH pc...and if you compromise the
ability of a pc to write data back...you can not only loose data...but,
damage the mdb file. This is the fundamental difference between using a file
share for the back end, or sql server (client/server) for the back end. In
both setups you can continue to use ms-access as front end...but in some
cases, if you can't ensure reliability connections...you need to move from a
file share to a true client-server setup.
