Closing Access files that are left open

A boolean flag in the BE with FEs regularly checking it are a common way of chucking everyone out - if that's what you're doing.
Her own FE can be made to close down when a hidden form with a Timer reads this flag as true.

Or are you wanting a mroe precise method than that?

Yes...please.

Well "Which one should I close first ?"
Are you just wanting to kill these?

Just killing the running instance wouldn't ideal - but if you have to I see no point in targeting the ldb file.

Are you able to prevent them from using the close button? here is an example, though hows C++ http://winfaq.msterminalservices.org/faqs2.cfm?id=468&category=2&sortby=date

links to thin.net

I have to go to a conference this morning EDT. It is 8:52am right now

I will be back by 1:00pm.

Thanks

We have many DB's that we use on TS/Citrix.  We have the system set up to log them out automatically w/ 1 hour of idle time. Never hurts anything.

Take a look at:
http://www.rogersaccesslibrary.com/download3.asp?SampleName=LogUsersOff.mdb
This sample illustrates how to automatically log all of your users out of an application for maintenance purposes.

http://www.rogersaccesslibrary.com/download3.asp?SampleName=LogUsersOffNonUse.mdb
This sample illustrates how to automatically log your user out of an application after a period of inaction.

Have you thought about deactivating the user's account and telling her she needs to see her her supervisor to get it reactivated?  You over create a reactivation form that needs several signatures and gets filed in the user's personal file.

jimpen...

I went to Terminal Services, she had disconnected from the services earlier and I closed the FE  ...unfortunately ...it did not close the BE...normally it does...I do not know why...

....so if I am going to do this manually, which one do I close first the LDB or the MDB ?

thenelson...

I am going to look at the files from the links you suggested...I will let you know...

deactivating the account would be something she would enjoy...she does not like to work...too much garbage to go into !

I do not know what she is doing...but now she is disconnected from Terminal Services and the BE is opened twice (with LDB and MDB)

She needs to log off the session not just disconnect.  The disconnect literally just hacks the connecction, the log off shuts it down gracefully.

The ldb is Access' locking file.
You shouldn't need to worry about it.

jimpen...

Yes.. I have sent an e-mail to her supervisor and her...with step-by-step (1. click on Start...etc)
...but apparently she cannot read or follow instructions.

LPurvis...
So I can close the MDB file...and not cause any harm ?

So you have straight TS and not Citrix.  Sorry to jump in then.  We do published apps and have better control with Citrix. I'll bow out now.

I'm not saying you can definately end the running mdb instance without any risk - but I'm saying I don't think trying to kill the ldb file first will be any better. :-)

LPurvis...
Well ....what is better ...
1. leaving the BE open indefinitely (through backups, compact/repair)
2. closing the BE manually

jimpen....

Do you think logging them off after certain idle time with TS is dangerous ?

What Jim is telling you about TS logout is the same as using winexit.scr or logging out manually when programs are open.  One at a time, the OS will post a dialog that the open program will be shut down and unsaved data will be lost.  When no one cancels the dialog, the program is shut down gracefully but not saving data (unless you put code in the DB to save data when the DB shuts down).  

Thanks to everyone who has contributed...

thenelson, LPurvis and jimpen...thanks for your input...I am going to try all of them to see which one suits this site. But all your ideas could easily suit other sites.


thenelson...thanks I passed your words to the boss...

 

I am going to make sure I can get the OK on logging out...gracefully...

then I am going to try some of the suggestions....

I will get back to everyone sometime today or tomorrow.

Well...

I logged into the terminal services as the user in question. I immediately logged out and it closed the database files and removed the disconnect message for that user.

I asked permission and did not get it...to logged her off...gracefully...after a period of time. She was idle for 2.5 hours at the time that asked permission (I got screen shots).

So I am going to "baby-sit" this user to make sure we get good backups. And hope that her idle time does not cause (because it is left vulnerable to) any damage to the database.

Thanks for all the input...