If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Record Locking Problem
I created an Access database on my computer, then took it over to another
department via flash drive and installed it on their server in a special folder. All of their personnel have full permissions for the folder, and the database defaults are set to "Shared", "Edited Record", and Record Level Locking is checked. That said, if more than one user opens the database (just the main form, not even to a record), I get a "more than one user is in the database" warning that I have to click on OK 31 times to make go away. After that, everything works. Any ideas on why 31 is a magic number? |
#2
|
|||
|
|||
Record Locking Problem
If you want multiple users to use a database then you need to split the
database. You would create a front end (FE) and back end (BE). The Tables go in the BE where everyone has access to the data. All your queries, forms, and reports go in the FE. If you are on a LAN, the BE can go on a netwrok drive but the FE needs to be loaded on each users computer. Read Joan Wilds article on splitting at www.jmwild.com "Todd K." wrote: I created an Access database on my computer, then took it over to another department via flash drive and installed it on their server in a special folder. All of their personnel have full permissions for the folder, and the database defaults are set to "Shared", "Edited Record", and Record Level Locking is checked. That said, if more than one user opens the database (just the main form, not even to a record), I get a "more than one user is in the database" warning that I have to click on OK 31 times to make go away. After that, everything works. Any ideas on why 31 is a magic number? |
#3
|
|||
|
|||
Record Locking Problem
For a larger database, I would. I have built two for our department that
have SQL BE's and Access FE's with auto FE updaters. However, for this one there are only about 6 users and I know Access is good for sharing up to about 12 users so I didn't do the "full Monty" on this one. My subject line here is kind of a misnomer, as it's not really become a record lock problem once you click OK 31 times. Nobody minds a notice saying "there are other people in the database", they just don't want it 31 times. I was thinking of setting up some code in the "On Open" event of the form to turn off warnings and turn them back on in the "On Close" event. I just feel like there's a glitch somewhere. "Golfinray" wrote: If you want multiple users to use a database then you need to split the database. You would create a front end (FE) and back end (BE). The Tables go in the BE where everyone has access to the data. All your queries, forms, and reports go in the FE. If you are on a LAN, the BE can go on a netwrok drive but the FE needs to be loaded on each users computer. Read Joan Wilds article on splitting at www.jmwild.com "Todd K." wrote: I created an Access database on my computer, then took it over to another department via flash drive and installed it on their server in a special folder. All of their personnel have full permissions for the folder, and the database defaults are set to "Shared", "Edited Record", and Record Level Locking is checked. That said, if more than one user opens the database (just the main form, not even to a record), I get a "more than one user is in the database" warning that I have to click on OK 31 times to make go away. After that, everything works. Any ideas on why 31 is a magic number? |
Thread Tools | |
Display Modes | |
|
|