By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,327 Members | 1,891 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,327 IT Pros & Developers. It's quick & easy.

Database Locks

P: 46
Hi All
I have a application used by 17 users.Each user has a shortcut to the centralized .mdb file.Some times when users tried to enter the values thru input form, a message pops up saying "The database has been placed is a state by user ?admin? on machine "machineno".When i close that application in that macine and restarts the application then every one can again able to start entering the values.Why is it happening.I have checked the mode access its shared ,no lock in database.Can any one tell me why is it happening so.This is my first question in this forum.If my way of question is wrong then do inform me, so that i can post in that manner.

Awaiting reply

Thanks
Regards
Dilip
Dec 5 '07 #1
Share this Question
Share on Google+
7 Replies


Jim Doherty
Expert 100+
P: 897
Hi All
I have a application used by 17 users.Each user has a shortcut to the centralized .mdb file.Some times when users tried to enter the values thru input form, a message pops up saying "The database has been placed is a state by user ?admin? on machine "machineno".When i close that application in that macine and restarts the application then every one can again able to start entering the values.Why is it happening.I have checked the mode access its shared ,no lock in database.Can any one tell me why is it happening so.This is my first question in this forum.If my way of question is wrong then do inform me, so that i can post in that manner.

Awaiting reply

Thanks
Regards
Dilip

A lock can occur on a database (the machine details of which you can see by opening the corresponding ldb file in notepad) for a miriad of reasons on a network particularly so if they are all accessing the one mdb centrally somebody for intance might have ctrl+alt+del to name but one example.

You should look at the concept of splitting your database into two db's frontend and backend give each user a frontend file and link to the backend database containing the data.

Have a read of this link

http://www.thescripts.com/forum/thread737435.html

Regards

Jim :)
Dec 5 '07 #2

P: 46
Hi

Thanks for the reply.Yes i have splitted the application into two parts that is FE and BE,where FE stands from front end which connects to BE, where BE stands for Backend which is the centralized database.And all users have shortcut to the FE part.But still some times the admin lock error arises.

Awaiting reply

Regards
Dilip






A lock can occur on a database (the machine details of which you can see by opening the corresponding ldb file in notepad) for a miriad of reasons on a network particularly so if they are all accessing the one mdb centrally somebody for intance might have ctrl+alt+del to name but one example.

You should look at the concept of splitting your database into two db's frontend and backend give each user a frontend file and link to the backend database containing the data.

Have a read of this link

http://www.thescripts.com/forum/thread737435.html

Regards

Jim :)
Dec 5 '07 #3

Jim Doherty
Expert 100+
P: 897
Hi

Thanks for the reply.Yes i have splitted the application into two parts that is FE and BE,where FE stands from front end which connects to BE, where BE stands for Backend which is the centralized database.And all users have shortcut to the FE part.But still some times the admin lock error arises.

Awaiting reply

Regards
Dilip
Does each user have there own frontend file I don't mean a shortcut targetting one frontend file I mean their own actual mdb frontend file

Jim
Dec 5 '07 #4

P: 46
Hi
Thanks for the reply.Every user has only a shortcut to the Front end file which is also centralized.Do i need to repair the database...or what else i need to check as it happens once in two days and when i restart theapplication its working fine.Please give me an idea


Thanks in advance

Does each user have there own frontend file I don't mean a shortcut targetting one frontend file I mean their own actual mdb frontend file

Jim
Dec 6 '07 #5

P: 4
The solution that we used here where we have around 20-25 users all using the same backend is that we created a folder for each user in a centralized location, from there we gave each user a full copy of the front end file. We then created a link on their desktops to make it look like everyone was using the same FE file, but they aren't infact they are linked to their own folder and thus the locks only happen on their front end. Further we created links for them Update Me! that will pull a standardized Most Recent Copy of the front end application so they can update when they get errors that I have fixed. Finally we have a master Update Them file that pushes all updates to unlocked DBs via a command prompt these are both .bat files that run in a command prompt window that echo.

Hi
Thanks for the reply.Every user has only a shortcut to the Front end file which is also centralized.Do i need to repair the database...or what else i need to check as it happens once in two days and when i restart theapplication its working fine.Please give me an idea


Thanks in advance
Dec 6 '07 #6

Jim Doherty
Expert 100+
P: 897
Hi
Thanks for the reply.Every user has only a shortcut to the Front end file which is also centralized.Do i need to repair the database...or what else i need to check as it happens once in two days and when i restart theapplication its working fine.Please give me an idea


Thanks in advance
Hi Ramdil,

In addition to what owyn999 says you give the user their own file not the shortcut to a single frontend file. You are not splitting it in the spirit of things because one frontend file is being accessed 17 times concurrently potentially and that is where any locks will be taking place in one ldb file on the server because some user or another has eited out wrongly or improperly or a simple network connectivity glitch. I have recently mentioned the same thing to another thread. If you are able to install the frontend file on the client then do so because that way you are running each file then 'per user' under its own steam on the clients installation of Access http://www.thescripts.com/forum/thread745608.html

In addition you are not having to drag the a potentially uncompacted high megabyte file over the network when they double click to open it, A local copy can open up locally to that client machine. The downside is 'distribution' of not having the frontends located conveniently on the server accepted but you could create a logon.bat at network user login to download the latest version from the server to the client. or write into your app version control to deal with that when it opens. Its whatever suits our networking arrangements.

Regards

Jim :)
Dec 6 '07 #7

P: 46
Hi

Thanks for the reply.If in mean time if you get you know any other options please let me know

Thanks in advance

Dilip


QUOTE=Jim Doherty]Hi Ramdil,

In addition to what owyn999 says you give the user their own file not the shortcut to a single frontend file. You are not splitting it in the spirit of things because one frontend file is being accessed 17 times concurrently potentially and that is where any locks will be taking place in one ldb file on the server because some user or another has eited out wrongly or improperly or a simple network connectivity glitch. I have recently mentioned the same thing to another thread. If you are able to install the frontend file on the client then do so because that way you are running each file then 'per user' under its own steam on the clients installation of Access http://www.thescripts.com/forum/thread745608.html

In addition you are not having to drag the a potentially uncompacted high megabyte file over the network when they double click to open it, A local copy can open up locally to that client machine. The downside is 'distribution' of not having the frontends located conveniently on the server accepted but you could create a logon.bat at network user login to download the latest version from the server to the client. or write into your app version control to deal with that when it opens. Its whatever suits our networking arrangements.

Regards

Jim :)[/quote]
Dec 11 '07 #8

Post your reply

Sign in to post your reply or Sign up for a free account.