Wrox Programmer Forums
|
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old May 19th, 2004, 03:35 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 126
Thanks: 5
Thanked 0 Times in 0 Posts
Default Back-end locking

Hello all,
I have a front end of a database that I send out and have everyone put on their desktop. The back end is on the network in a folder that everyone has read & modify rights to. Whenever someone gets in the front end and is accessing the info from the back end, it locks everyone else out giving them an "already in use by another user" error. Why is this doing this?

Thanks!
Laura

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!
__________________
Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!
 
Old May 19th, 2004, 04:59 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,998
Thanks: 0
Thanked 3 Times in 3 Posts
Default

Hello,

Both front-end and back-end are access DB's, correct? Access generates a .ldb file which is a locking file that locks the database whenever someone accesses it. It's not transactional like SQL, where many users can access and even edit a table simultaneously.

Brian
 
Old May 20th, 2004, 08:17 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 126
Thanks: 5
Thanked 0 Times in 0 Posts
Default

Yes, both front end and back end are in Access XP. It is creating the lock file on the front end, which I understand, but why wouldn't it create one on the back end and let others in it at the same time? I have other databases that are not split and they create the lock file but also let multiple users in at the same time.

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!
 
Old May 20th, 2004, 09:36 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

If it is not creating one on the back end side, probably you have that file set up to open exclusive by default.

Go to tools/options / advanced and make sure that it is NOt set to exclusive. the front end should be opposite if it resides on the client.



Sal
 
Old June 8th, 2004, 07:45 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 126
Thanks: 5
Thanked 0 Times in 0 Posts
Default

Thank you for your reply Sal,
I looked at each computer that uses this database. Each computer is set as a default to open as shared and not exclusive. This works fine on my machine. When I open the front end, it creates the lock file for both the front end and back end, but the other computers do not. We all have the same network clearance to that folder, the same default settings, & the same version of office XP, so I'm not sure why it is doing this.
Any more ideas?

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!
 
Old June 8th, 2004, 08:14 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

A lock file should be present if you have set the back end properly. Make sure that the backend as well as front end is creating a lock file (actually you do not a lock file on the front end if it resides on the local PC)

Your problem is with the back end not the front end.

I do not know exactly what you mean by:

 
Quote:
quote:it creates the lock file for both the front end and back end, but the other computers do not.


make sure that all datasources to all forms and reports are set to EditedRecord under recordlocks propertiy, also under options/advanced tab, make sure that under

"Default Record Locking" you ckeck Edited Record
"Default open mode" check Shared
Check the box for Opend databases using record level locking.

Do this for both front and backend.

Also, try to open a copy of your front end on another computer ansd see if it creates the lock files.





Sal
 
Old June 9th, 2004, 07:52 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 126
Thanks: 5
Thanked 0 Times in 0 Posts
Default

Sal,
I previously checked these settings on every computer for both the front end and back end and they were all set to the settings you mentioned.
What I meant about the lock files is that when I open the front end (which is saved to my desktop) on my PC, it creates a lock file on my desktop for the .mde file and also creates a lock file for the back end out on the network where it (the back end) is stored. When opening the .mde file on others computers, it creates the lock file for the .mde file (front end) that is located on the desktop, but doesn't create the lock file for the back end out on the network. This is what is confusing me because if mine and their setting and network clearance (on that folder)is the same, I shouldn't be having this problem.
Do you think me creating this in Office 97, then converting it to Office XP could have anything to do with it?

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!
 
Old June 9th, 2004, 09:59 AM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

If it is because of 97 try importing items into a new DB, but I dout that that would be the problem. Even if 97 did not create lock files.

Are you sure that the back end has been converted as well? Wild guess.



Sal
 
Old June 9th, 2004, 08:49 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Try importing all of your tables into a new access database, in case it is the 97-XP upgrade.



Sal
 
Old June 14th, 2004, 07:44 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 126
Thanks: 5
Thanked 0 Times in 0 Posts
Default

I imported all the tables into a new database and we are still having some issues. This is really weird...and driving me a little crazy!

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!





Similar Threads
Thread Thread Starter Forum Replies Last Post
Front end Vs Back end ricmar Access VBA 3 May 27th, 2008 02:36 PM
Ms Access front End with Oracle 10g Back End rahul123 Oracle 1 July 9th, 2007 01:03 AM
Oracle back-end MS-Access 2003 client front-end Corey Access 2 February 16th, 2007 08:31 AM
Oracle Back End - MS Access Front End - Multi User ckaliveas Oracle 1 February 1st, 2007 06:00 AM
Re-linking the front and back end Scripts82 Access VBA 2 February 24th, 2006 12:26 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.