Just to help this,
Think of a Excel sheet you place on that server, but that server does NOT
have excel installed.
When you run and load excel on your computer, does the server magically now
start running excel?
the same applies to ms-access. The processing, and code, and execution
occurs on YOUR machine. In fact, your "back end" mdb file is placed on that
server, but you never did have to install ms-access on that server.....(so,
how is it that server going to run ms-access when ms-access never was
installed????).
Of course, ms-access is smart, and DOES NOT always read in the whole file
from the disk drive. So, if you have 100,000 records, and retrieve ONE
record, then ms-access can use index to determine "WHERE" on the disk drive
that ONE record is..and then simply requests the disk drive to ONLY load
that part of the file.
The fact of the file being on drive "c:"....or some network share DOES NOT
change how ms-access reads ONLY that one part of the file....
So, if ms-access has to read "all" of the file when the mdb is on drive c:,
then it will continues to do so if you put the mdb on a file share.
So, if ms-access has to read the whole file, and a network is between you
and the file...the obviously the whole file has to pass "through" that
network.
Since ms-access does it best to use index, and read as little data as
possible, then often the WHOLE table is NOT transferred.
However, all data, and all processing occurs on your computer, and that mdb
file is just plain Jane file sitting on he disk drive. The fact of that disk
drive be on your local c: drive, or a drive halfway across the world that
you opened...does NOT change the behaviours as to how ms-access runs.....
ms-access does not *always* read in the whole table, so therefore, the whole
table is not transfered from that file into your comptuers memeory. What
that file is located does NOT change this behavour....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com