Since ms-access is a file share database, then no software, or "engine" is
running on the server.
When you use a client to server based engine, then all users on the network
NEVER actually open the data files. The ONLY thing that opens the data files
is the database server (that server engine is running on the server pc). So,
to back up a file, you either have to temporality stop the database server,
or use the option to de-tatch the data files from the database sever. This
means virtually all client to server database systems usually have some
maintains mode, or at least a utility to "stop" the database server so all
files can be backed up.
In the case of a JET file share (a shared mdb file), there is NO software
running on the server. Since you don't have JET installed on the server, and
JET never runs on the server, then there is no system, or software to "stop"
or de-tatch from the files on the server. Hence, to backup those files, then
you must ensure that ALL USERS are out of the system. When you run oracle,
you only run ONE copy on the server. When you run a JET, EACH USER IS
RUNNING a copy of the database system (in this case JET). So, all processing
occurs on each work station, and thus you must have each user "stop", or
de-tach their database system (jet) from those files.
Remember, a JET file share is just a normal file. If users have a word
document open on the sever, or a Excel file open on the server, or a JET/mdb
file open on the server, then the backup software will skip that file.
So, no, there is nothing special at all you have to do when backup up that
mdb file, but you do need to make sure that everyone is out of the file, and
not running the application. So, it is like word, or Excel...you simply have
to make sure no user has that file open.
