No. As is pointed out in these newsgroups on generally a daily basis: This
is definitely not a good way to set up and deploy a multi-user Access
database.
Your application should be split into two database files: The first, a
back-end containing the tables of shared data, which will be located on your
server-computer; the second, a front-end database containing all other
objects (queries, forms, reports, macros and modules - plus links to tables
in the back-end database). This front-end database should be copied to each
user's local hard drive.
Updating the front-end database on each user's hard drive can be
accomplished by teaching your users how to drag and drop a file from one
folder to another, creating and placing a batch file on each user's computer
that will do the copying, all the way to using an automated updating scheme
such as the one that Access MVP Tony Toews has made available at his web
site:
http://www.granite.ab.ca/access/autofe.htm
--
Cheryl Fischer
Law/Sys Associates
Houston, TX
> What I currently do is have a computer that is setup as
> the server computer(meaning it has the main copy of the
[quoted text clipped - 5 lines]
> What is the best way to have concurrent users?
> Any input would be greatly appreciated?
Hi.
Even I need the answer for that..Pls. do mail me if u happen to get the answer to bijuk3@yahoo.co
with regard
biju.k
Douglas J. Steele - 30 Dec 2003 11:32 GMT
Didn't you read Cheryl's excellent response?

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)
> Hi..
>
> Even I need the answer for that..Pls. do mail me if u happen to get the answer to bijuk3@yahoo.com
If you post to the newsgroup, you come back to the newsgroup to get your
answer. Don't expect people to send private email!