Front & End Users

  • Thread starter Thread starter Linda
  • Start date Start date
L

Linda

Good day all!

I have now put my database on the server for 2 other girls
to use. This is for file management. If we open it all
at the same time, and work in it such as adding file names
and so on, will it save it all or is that not a good
idea. I have created a shortcut on their desktop, but
it's only when you go directly to the root that you see a
padlock on the file.

Can someone tell me what is best?

Many kind thanks
Linda
 
For multi-user applications, it is a good practise to "split" the
application into the data part, and the application part.

This allows you to develop and test and work on a next great version of your
software. That next great version might be just a few new forms, or a few
new reports. None the less, with a split arrangement you can SAFELY develop
on a separate version of the code. You can even work with a separate copy of
the data. When you are ready to deploy, you "link" your new front end to
the production back end (data file).

Not only is a split approach far better from a development point of view,
but it is also far more reliable setup.

Check out:

http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm
 
Good day all!

I have now put my database on the server for 2 other girls
to use. This is for file management. If we open it all
at the same time, and work in it such as adding file names
and so on, will it save it all or is that not a good
idea. I have created a shortcut on their desktop, but
it's only when you go directly to the root that you see a
padlock on the file.

Can someone tell me what is best?
Click to expand...

It is NOT a good idea for multiple users to share the same frontend.

Use Tools... Database Utilities... Database Splitter Wizard to split
the database into a "frontend" (with the forms, reports, queries etc.)
and a "backend", with just the tables. Give each user a copy of the
frontend, on her own machine; the backend should be on a (safe,
stable!) shared folder.
 
Back
Top