Auto Close Database (1 Viewer)
- Thread starter bhelmy
- Start date
Minty
AWF VIP
- Local time
- Today, 07:31
- Joined
- Jul 26, 2013
- Messages
- 10,371
If this is the front end then you shouldn't have users in it on a network share. Each user should have their own local copy of the front end. If you haven't split it to a front-end / back-end you should to avoid corruption and record locking issues.
If you want to kick someone out how should the task deal with any open forms? Unsaved data? Edited records ?
If you want to kick someone out how should the task deal with any open forms? Unsaved data? Edited records ?
missinglinq
AWF VIP
- Local time
- Today, 02:31
- Joined
- Jun 20, 2003
- Messages
- 6,423
You need to address the issues Minty has brought up, before doing anything else! Having multiple users sharing a single, non-split database, sitting on a network drive, or using a split database, but having them link to a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.
Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally dozens and dozens of reports of non-split databases, or split databases, using links to a single Front End, causing these kinds of problems as well as massive data lose! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!
The record, by the way, was a Non-Split db that had been working, without problems, for 12 years! It then started exhibiting all of the symptoms listed above and continued to do so until the app was split.
If your Database isn't really important, which is to say if data-loss isn't important, and the app being down won't cost you production time loss, then by all means leave it non-split.
Once this is attended to, here is a link to a hack for kicking 'idle' users out:
http://msdn2.microsoft.com/en us/library/bb243861.aspx
Linq ;0)>
Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally dozens and dozens of reports of non-split databases, or split databases, using links to a single Front End, causing these kinds of problems as well as massive data lose! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!
The record, by the way, was a Non-Split db that had been working, without problems, for 12 years! It then started exhibiting all of the symptoms listed above and continued to do so until the app was split.
If your Database isn't really important, which is to say if data-loss isn't important, and the app being down won't cost you production time loss, then by all means leave it non-split.
Once this is attended to, here is a link to a hack for kicking 'idle' users out:
http://msdn2.microsoft.com/en us/library/bb243861.aspx
Linq ;0)>
