share the access database on the network

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

SG - 24 Mar 2005 21:49 GMT

Hi,

I created an access program on a network drive. I don't know if it can be
shared by 20 users on the network at the same time without splitting it into
FE/BE, I like to make this as simple as it can.
I tried 2 users, it seems to work. But I like to confirm this.

Thanks in advance,
Sarah

Reply to this Message

Douglas J. Steele - 25 Mar 2005 01:09 GMT

Go to the trouble of splitting it. You won't regret it!

Having multiple people opening the same database significantly increases the
risk of corruption.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Hi,
>
[quoted text clipped - 5 lines]
> Thanks in advance,
> Sarah

Reply to this Message

Tony Toews - 25 Mar 2005 01:52 GMT

>I created an access program on a network drive. I don't know if it can be
>shared by 20 users on the network at the same time without splitting it into
>FE/BE, I like to make this as simple as it can.
>I tried 2 users, it seems to work. But I like to confirm this.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Reply to this Message

SG - 28 Mar 2005 18:21 GMT

Appreciate both Douglas and Tony's response. I guess I have to split our
database. Just don't quite follow update the data from FE instead of BE, I
will read some notes and if I have a question I will come back to you.

Thanks,
Sarah

> Hi,
>
[quoted text clipped - 5 lines]
> Thanks in advance,
> Sarah

Reply to this Message

Klatuu - 06 Apr 2005 19:01 GMT

There should be no data in the front end and nothing but data in the back
end. Use the database splitter to do the split, and it will do exactly this.
If your mdb is xyz.mdb, it will create xyz_be.mdb.

Put xyz_be.mdb on the server and a copy of xyz.mdb on each user's computer.
DO NOT RUN THE FRONT END FROM A SERVER AND DO NOT ALLOW USERS TO SHARE A
FRONT END.

There are some other issues regarding record locking, but they are too
involved to go into here.

> Appreciate both Douglas and Tony's response. I guess I have to split our
> database. Just don't quite follow update the data from FE instead of BE, I
[quoted text clipped - 11 lines]
> > Thanks in advance,
> > Sarah

Reply to this Message

Rod @ CLA - 21 Apr 2005 20:14 GMT

SG,

There is a simple way to distribute an updated MDE after you split the DB.
We use a simple batch file:
(everyone gets a mapped drive to Q: where the FE and BE are)
********************
if not exist "%userprofile%\paperflow" md "%userprofile%\paperflow"
q:
copy /b /y CLAlocal.mds "%userprofile%\paperflow"
c:
cd "%userprofile%\paperflow"
del clalocal.ldb
start CLALocal.mde
exit
*********************

This way when we make updates to the FE, it gets automatically distributed
to the user the next time they launch the app.

Rod

Reply to this Message