[AccessD] error & structure: Please Help!!

Hello Jim And Marty,

thanks for the tips.

I will check this out.

Pedro Janssen



In antwoord op:

> From: MartyConnelly <martyconnelly at shaw.ca>
> To: Access Developers discussion and problem solving
> Date: Wed, 23 Nov 2005 17:43:16 -0800
> Subject: Re: [AccessD] error & structure: Please Help!!
> 
> 
> You can force out Idle Users and also a similar method with a timer and 
> hidden form and a small field in a table
> can be used to force everyone out with a 5 minute warning
> 
> Candace Tripp has an example mdb "Detect and Logoff Idle Users"
> http://www.candace-tripp.com/pages/access_downloads.aspx
> 
> 
> HOW TO: Detect User Idle Time or Inactivity in Access 2000
>    http://support.microsoft.com/?id=210297
> 
> use Const IDLEMINUTES = 20 (instead of the 1 minute setting shown in the 
> Knowledge Base article),
> and  do not display a message box as shown in the  article, since 
> message boxes are modal and this would defeat any attempt to close:
> 
> Sub IdleTimeDetected(sngExpiredMinutes)
>    'Dim strMessage As String
>    'strMessage = "No user activity detected in the last" & vbCrLf
>    'strMessage = strMessage & sngExpiredMinutes & " minute(s)!"
>    'MsgBox strMessage, vbInformation, "No Sign of Activity!"
>    Application.Quit acSaveYes
> End Sub
> 
> 
> Jim Lawrence wrote:
> 
> >Hi Pedro:
> >
> >One thing you can do is when you get the BE recovered. Check to see how
> >database is being used. Some of the problems that I had were:
> >
> >1. Some users never logged off and just left everything running.... result
> >in extra exposure and halted backups.
> >2. One user simply used the off and on button when ending for the day.
> >3. One of the local IT guys would re-boot the server without getting
> >everyone logged off. 
> >
> >I am not suggesting that these are the issues at your site but a similar set
> >of problems that that physically affect database I/O would continuously
> >corrupt your BE.
> >
> >HTH
> >Jim
> >