Split Database not allowing more than one user

  • Thread starter Thread starter Thorson
  • Start date Start date
The point of splitting the database is to allow multiple users to
access the back end (i.e.: the data) at the same time.
Click to expand...

And each user should have an individual copy of the front end.
 
So everyone needs read/write/create permissions to the folder the BE is in?
I can't give someone read-only?

In the 2007 database from my understanding I can not create individual users
permissions. Is that correct? So how do I limit the users' permissions?

I'm not sure what the locking (.LDB) file is. I am new to this especially
the lingo.

Thank you for your help!
 
Whenever a user connects to an Access database, a locking file is created.
This file has the same name as the database, but with an extension of .LDB
instead of .MDB (or .MDE or .ACCDB or .ACCDE) and exists in the same folder
as the database itself. (and no, it's not possible to change its location)
This locking file is how Access controls concurrent updates to the database.
If a user only had read access, with no write (and create) permission, then
no other user will be able to update the database.

You can leave the database in MDB format, and Access 2007 will then still
support user-level security. It's only in the ACCDB format that there's no
ULS.
 
You can leave the database in MDB format, and Access 2007 will
then still support user-level security. It's only in the ACCDB
format that there's no ULS.
Click to expand...

Yet a whole lot of people (and I'm not referring just to lunatics
like Aaron Kempf) seem invested in propagating the myth that ULS
(and replication) are not supported at all in A2007. Any time I see
someone say that I immediately think "this is not someone who gives
reliable advice -- I will discount anything I see from them in the
future."
 
David W. Fenton said:
Yet a whole lot of people (and I'm not referring just to lunatics
like Aaron Kempf) seem invested in propagating the myth that ULS
(and replication) are not supported at all in A2007. Any time I see
someone say that I immediately think "this is not someone who gives
reliable advice -- I will discount anything I see from them in the
future."
Click to expand...

So I'm safe? (for now, at least...) <g>
 
Ok, that all makes sense. So the only way to get user-level security is to
change it to .MDB, and therefore I would loose the database features that are
only available in 2007?

How do I change a 2007 database to .MDB?
 
So the only way to get user-level security is to
change it to .MDB, and therefore I would loose the database
features that are only available in 2007?
Click to expand...

Other than multi-value fields (which I can't imagine any
professional developer actually using), what features does ACCDB
have that MDB lacks?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Multi-user database deployment 2
Trust Center Issue 2
Secure back end database 1
Security newbie 1
Putting restrictions in a split database 1
Disappearing Users 1
fastest way of distributing a split and secured database 1
Allow more than one user on a database 3

Back
Top