Myra
Sorry you did not get a prompt response. Many of us are trying to finish up workloads before the holidays (me being one of those).
Your IT people are morons or seriously under-qualified. They should be able to delete a locking file on a server.
That said, Yes, you need to split the database. The days of crossing fingers and hoping a multi-user non-split database will not crash or lock went bye-bye with version 95...or maybe it was 97 especially when opened by later versions of Access. I'd rather reach for a stove knob while holding my hand under the running water out of the kitchen faucet (which I actually did many years ago and barely lived to tell about it).
Yes, .mdb files opened in 2007/2010 have a tendency to corrupt especially if the compact on close option is set and the Office suite is not updated.
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT http://thatlldoit.com
MS Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My Nothing-to-do-with Access blog
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of myrafly@yahoo.com
Sent: Friday, December 20, 2013 9:54 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Persistent locking file.
Twice in as many days we've had people locked out of their database when it got corrupted. I will advice them on front end/ back end design after the fact. I am wondering how we can get these lock files deleted. I always thought IT had special delete magic, but our IT department has no such tricks. By the way this has happened on 2010 and 2007 (mdb unconverted). I wonder if there is something funky about how our network is set up...
Thanks everyone.. (Happy Holidays!)
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar