John
It might have been the corruption. There is software out there that will sometimes unlock an .LDB file so you can delete it. The one I use is at http://ccollomb.free.fr/unlocker
If that doesn't unlock it your network guy should be able to do it. Otherwise, if it is possible call someone to reboot the user's computer. That should free up the LDB file.
Bill
--- In MS_Access_Professionals@yahoogroups.com, "jfakes.rm" <jfakes@...> wrote:
>
> Bill,
> I use the InactiveShutdown in all of my databases and it's been a life saver. Some users complain about getting kicked out after 30 minutes (my default) but I tell them its a security concern. In this example, I had a user log on remotely (from a wireless connection) and the db corrupted. I have a "keep open" form that keeps a permanent connection open to the backend to speed things up. Well the user went to lunch and when I tried to work in the be, I couldn't because Access said someone was using it. I tried to delete the .ldb and the users frontend so I could do my work but no luck. So I was trying to see if I could automate kicking the user out of the frontend so I could do some work when I found out the user was out to lunch. I guess since the fe became corrupt, the inactive shutdown didn't work, very strange.
>
> John F
>
> --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> >
> > John
> >
> > There is a sample database in our files called InactiveShutdown. It includes forms and shows how to use a timer event to check if the database has been idle for a given time. If so, the database closes itself.
> >
> > Regards,
> > Bill Mosca, Founder - MS_Access_Professionals
> > http://www.thatlldoit.com
> > Microsoft Office Access MVP
> > https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
> > My nothing-to-do-with-Access blog
> > http://wrmosca.wordpress.com
> >
> >
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "jfakes.rm" <jfakes@> wrote:
> > >
> > > I've seen processes on how to remotely close a frontend but I thought I'd ask the experts on this site as to the best way to do this.
> > >
> > > It happened again yesterday, I had a user log into a frontend and edit a form (I know, don't let users edit forms, but thats the way the db was set up. I also know not to share a fe with more than one user, but...) Anyway, the user walked away from her computer leaving the fe locked up. The other user tried to get into the db but got the dreaded admin locked error. I suggested adding another fe in, but eventually the user closed the db and the issue was resolved.
> > >
> > > In the future if this happens, I want to be able to safely close that frontend. Whats the best way to do this remotely? I do not have special permissions on the server to close it.
> > >
> > > John F
> > >
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (12) |
Tidak ada komentar:
Posting Komentar