Second (Multiple) user cannot open MDB from explorer.

[Beeawwb]

Hi all,

I have a database I've just created and multiple users may want to access
it. I've set up the user level security, assigned everybody usernames and
passwords, that's fine. The problem is, 2 users cannot open the database at
once...through explorer.

If user 1, let's say me, opens the file and creates the .ldb record locking
file (which, I'm not sure why it's creating, because I have record locking as
"No locks" in Options->Advanced) nobody else can open the file in explorer by
double clicking.

If you go through Access, choose open and then select the file, it will open
fine and there's no problems.

Before it gets asked, I should mention that all users have read, modify,
execute and delete permissions for this folder.

Thanks in advance for your wisdom,

-Bob

 

[boblarson]

Just an FYI -

If you are using a SHARED database by anyone it should be a Frontend/Backend
split database with EACH user having a copy of the frontend on THEIR
computer. This will eliminate your issue as well as reduce the possibility
for corruption.


Here's a link with more info about that:

http://members.shaw.ca/AlbertKallal/Articles/split/index.htm



--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________

 

[Beeawwb]

Thanks for the quick response Bob,

I actually found a way around the issue by creating a batch file to launch
the database and access my security file. When I did that, multiple users
were able to launch the database at the same time.

Your solution makes much more sense though. Splitting and sharing multiple
front ends makes much more sense, as I can the customise the menus for each
user based on what they need to do.

Thanks again.

-Bob

 

[boblarson]

It would take some extra coding but you could. You need to keep things
somewhat simple to be able to have like one master copy and you do the
changes there and then distribute the changes. However, if you look at my
website, I have a Frontend Auto Update Enabling tool which will let you
distribute the changes in the frontend by

1. If the user opens the database and you have changed the version number in
the frontend master and the backend, they will get a message that the
database has changed and the database needs to close and then reopen.

2. It will then delete the old file and

3. copy the new file from the master location and

4. automatically reopen the database for the user

You can get the tool here:

http://www.btabdevelopment.com/main/AccessTools/tabid/78/Default.aspx

Be sure to download the documentation too.

--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________

 

[Beeawwb]

I just wanted to add, I've finished reading the article you linked, and it's
an extremely valuable piece of information. I've learned a lot about the
concepts, and it's given me some great ideas moving forward! To anybody who
comes across this post in the future, I highly suggest reading the article on
splitting.

Thanks again.

 

[John W. Vinson]

Hi all,

I have a database I've just created and multiple users may want to access
it. I've set up the user level security, assigned everybody usernames and
passwords, that's fine. The problem is, 2 users cannot open the database at
once...through explorer.

If user 1, let's say me, opens the file and creates the .ldb record locking
file (which, I'm not sure why it's creating, because I have record locking as
"No locks" in Options->Advanced) nobody else can open the file in explorer by
double clicking.

If you go through Access, choose open and then select the file, it will open
fine and there's no problems.

Before it gets asked, I should mention that all users have read, modify,
execute and delete permissions for this folder.

Thanks in advance for your wisdom,

-Bob

Split your database... now!

Each user should have their own copy of a "frontend", either a .mdb or better
..mde file with links to a shared "backend", containing only the tables.

See http://www.granite.ab.ca/access/splitapp.htm for a description.

John W. Vinson [MVP]

 

[Beeawwb]

I actually ended up implementing that front end version updater last night
before reading your post this afternoon. Very much the way I'm wanting to go,
since most of my projects end up getting regular updates as we go along.

Thanks again for your assistance.