Jumat, 19 April 2013

RE: [MS_AccessPros] Remote shut down of a Front End db

 

Actually Bill, I'm thinking that's where I got my idea from years ago. Thanks so much. I've learned so much from you and John and the rest of the group I don't even know where I got what any more.

Respectfully,
Liz Ravenwood
Programmer/Analyst
Super First Class Products
B/E Aerospace
O: 1.520.239.4808
www.beaerospace.com

-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
Sent: Friday, April 19, 2013 8:52 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Remote shut down of a Front End db

Funny you should mention that, Liz. I wrote an article on how to do exactly that. It's on my site at http://www.thatlldoit.com/Pages/howtosarticles.aspx

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, Liz Ravenwood <liz_ravenwood@...> wrote:
>
> John, is there any way you can have the users run a script that they only get a copy of the front end to their local drive? That way, they each run their own version of the database and don't impact each other. The data of course would still be linked in the back end.
>
> Respectfully,
> Liz Ravenwood
> Programmer/Analyst
> Super First Class Products
> B/E Aerospace
> O: 1.520.239.4808
> www.beaerospace.com
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
> jfakes.rm
> Sent: Friday, April 19, 2013 6:32 AM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Remote shut down of a Front End db
>
> 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
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
> This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
>

------------------------------------

Yahoo! Groups Links

This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

__._,_.___
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (6)
Recent Activity:
MARKETPLACE


.

__,_._,___

Tidak ada komentar:

Posting Komentar