.ldb and Multi-users...

[Catchin'' On]

We have our 2003 MS database on a shared folder on our server. When the
users open the database a .ldb file appears in the folder. At times we can
only have up to three users open the .mdb file at the same time, but after
three users have the .mdb file open no others can open the file.

How can I enable access so that more users can open and add data to the
database at the same time?

I'm not sure if it matters, but I have user-level security set up with 3
workgroups, one with admin permissions (management), one with read, write,
execute, delete, permissions (sales), and one with read only (the shop).
Also, everyone has full rights to the folder on the server.

 

[Tom van Stiphout]

What Arvin said, and the MDW file can stay on the server and is
referenced in the shortcut with the /wrkgrp command line switch. If
you created three MDW files you probably did not first download,
study, and fully understand the Microsoft Security FAQ. Still highly
recommended because this is an advanced topic and easy to get wrong or
incomplete.

-Tom.
Microsoft Access MVP

 

[Catchin'' On]

Thanks for the replies...
Tom, I guess I worded it wrong I only have one MDW file, but three groups
with different permissions. Not sure how to word it but the users and groups
log on is working great. The part that is still not working is how multi
users cannot open the db at the same time.

So I have some questions about splitting the db. I understand that when I
split the db with the database splitter and it creates a back end (be) file
of the db that contains all the tables and relationships and a front end file
with basically everything else.

1. If I split the db when it is in the shared foler on our server and place
the back end file in the same folder will the front end file be the original
..mdb file?

2. If the front end file is the original file do i just drag and drop a copy
of that front end file to each user's personal computer's desktop for easy
access???

3. If I do this when they open the file on their desktop and enter lets say
an order, will it will load the data into the backend file still located on
the server's shared folder?

4. So what if i need to modify the design of a form or add a new form or
report??? I can modify the front end copy on the server, the re-drag and drop
the new front end file to each users desktop? Is it that easy???

5. And to modify a table in the back end file i would have to open the back
end file on the server and then just save it?

6. I'm not really worried about users being able to modify the database
because i have set up each users permissions. Is there another reason i
would want to convert an MDE file?

Sorry so many questions, but i have a ton of time invested and don't want
any huge issues or lost data. It will be the first db I developed so I'm
pretty excited, but want to get it right the first time.

Thanks again you guys... I love having a place to ask question and get the
right answers. You guys have really helped me throught the ENTIRE process of
developing the access db. Heck, when i first opened MS access for the first
time in Dec. i had no idea wha i was getting into. You all helped me keep my
santity.

Thanks again,
-H-

 

[Arvin Meyer MVP]

Thanks for the replies...
Tom, I guess I worded it wrong I only have one MDW file, but three groups
with different permissions. Not sure how to word it but the users and
groups
log on is working great. The part that is still not working is how multi
users cannot open the db at the same time.

So I have some questions about splitting the db. I understand that when I
split the db with the database splitter and it creates a back end (be)
file
of the db that contains all the tables and relationships and a front end
file
with basically everything else.
Yes

1. If I split the db when it is in the shared foler on our server and
place
the back end file in the same folder will the front end file be the
original
.mdb file?

Yes, except that now there are links to the tables on the back-end instead
of the actual tables.

2. If the front end file is the original file do i just drag and drop a
copy
of that front end file to each user's personal computer's desktop for easy
access???
Yes

3. If I do this when they open the file on their desktop and enter lets
say
an order, will it will load the data into the backend file still located
on
the server's shared folder?
Yes

4. So what if i need to modify the design of a form or add a new form or
report??? I can modify the front end copy on the server, the re-drag and
drop
the new front end file to each users desktop? Is it that easy???

You modify the design on one copy of the database, then put it on the server
and replace each person's front-end.

5. And to modify a table in the back end file i would have to open the
back
end file on the server and then just save it?

Yes, while no one is connected to the back-end

6. I'm not really worried about users being able to modify the database
because i have set up each users permissions. Is there another reason i
would want to convert an MDE file?

No, if your security is working fine, test it after the split and if OK
leave it the way it is.

Sorry so many questions, but i have a ton of time invested and don't want
any huge issues or lost data. It will be the first db I developed so I'm
pretty excited, but want to get it right the first time.

Make sure you back up everything before you attempt to split, then again if
you decide to make any other changes.