David A Gibson
davidalangibson2010 at gmail.com
Tue Jan 14 14:13:29 CST 2014
A word of caution when sharing DBs between PCs & Macs. One year we had an MS Access 2010 .accdb shared between about 40 users with as many as 15-20 accessing it at one time without any problems. The next year or the one after, we did it again and had all kinds of file corruption problems. Turns out that whenever a Mac user running Access in Parallels would manage to lock their computer without exiting the DB it would corrupt data tables. Had a lot of lost work before we figured it out. David Gibson -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Tuesday, January 14, 2014 2:01 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Back-End DB is locking...WHY?! John, Anytime any JET database is opened, a locking file is created. If a LDB file cannot be created because of permissions, the DB is opened exclusive. One thing to watch out for; DB's with the same base name, but a different extension. Ie. myApp.MDW myApp.MDB When you go to open myApp.MDB, with myApp.MDW being the workgroup file (which is also a JET database), both get the same LDB file name; myApp.LDB and all kinds of weird stuff will happen. So check for that first. Then with everyone out, delete any LDB files. Make sure the DB open mode is shared. And by the way, you can share a DB fine, it's just not recommended and not the most efficent for a number of reasons. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark Sent: Tuesday, January 14, 2014 02:27 PM To: Access Developers discussion and problem solving Subject: [AccessD] Back-End DB is locking...WHY?! I just inherited a program from someone else...a non-programmer, who used some of MY original code and thought she was a programmer...very sore subject...especially today. Anyhow, she had three people sharing a single Access DB (.accdb) on a common network drive. Somehow it was working for them...until it wasn't. The did some cleaning up of their file structure the other day, and they renamed some directories, and it no longer worked. I told them that I was surprised it was working in the first place, and that I wouldn't spend time figuring out "why" but I'd fix it the right way. To make a long story short, I got all the tables into a single DB and then used database splitter to create a front-end/back-end situation. This is the first time however, that I am seeing a back-end gain a lock file (.laccdb). I split the DB, yet it is still a single-user program...and I have no idea why. I suspect...but I'm trying to keep an open mind...it has something to do with the fact that it was a "front-end" program of my original that she used at the beginning...her beginning anyhow. Does anyone have any idea what I can look at to prevent...stop...this from happening? Please help someone who is having a very bad day... Thanks in advance! John W Clark Computer Programmer Niagara County Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com