Database Corruption over the LAN

Hello,

I created a database that I'm trying to distribute to a
few users over a LAN. Some access it through different
shared drives--example, person in CT accesses it through
the T:\ drive...the person in NY access through the O:\
drive...etc. I know this shouldn't matter, but the
database keeps getting corrupted over the LAN.

My question is: Are there certain prerequisites that
need to happen so that the database can be shared
properly with others in different geographic locations?
For example, one person may be running Access 2000,
another is running Access XP. Do they need exactly the
same configuration...service packs and all? same Jet
Engine?

Is there a checklist of items to watch for?

Thanks for you help.
D.

I would surprised that you can get any useable performance over a wan (wide
area network).

If your remote users have no troubles using the database, then you must have
a very good wan indeed.

You need to run a split database. That means EACH USERS gets their own copy
of the front end. Preferred, this front end should be a mde, and NOT a mdb
file.

Further, you should not use drive mapping to link the front end to the back
end, but use a unc path names like:

\\YourDataServer\YouDir\MyBackEndData.mdb

You can read up on splitting he
http://www.granite.ab.ca/access/splitapp.htm

You can read up on prevent corruptions he
http://www.granite.ab.ca/access/corruptmdbs.htm

Splitting will fix most of your reliability problems.

However, for a wan, you might want to read the following:
http://www.attcanada.net/~kallal.msn/Wan/Wans.html

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.attcanada.net/~kallal.msn

Thanks Albert. I am going to look this information
over...I appreciate the help.

Take care, D.
-----Original Message-----
I would surprised that you can get any useable
performance over a wan (wide
area network).

If your remote users have no troubles using the
database, then you must have
a very good wan indeed.

You need to run a split database. That means EACH USERS
gets their own copy
of the front end. Preferred, this front end should be a
mde, and NOT a mdb
file.

Further, you should not use drive mapping to link the
front end to the back
end, but use a unc path names like:

\\YourDataServer\YouDir\MyBackEndData.mdb

You can read up on splitting he
http://www.granite.ab.ca/access/splitapp.htm

You can read up on prevent corruptions he
http://www.granite.ab.ca/access/corruptmdbs.htm

Splitting will fix most of your reliability problems.

However, for a wan, you might want to read the following:
http://www.attcanada.net/~kallal.msn/Wan/Wans.html

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.attcanada.net/~kallal.msn


.