Close Form for Inactivity

[Bonnie]

Hi there! Using A02 on XP and loving the newsgroups!!! I'm
having a problem with occasional lockups on a few shared
DB's. Have dozens of users and about 6 DB's that are used
frequently by many. DB's are frontends and tables are all
in a backend DB. Sometimes I'm told of a "Cannot save
record at this time, currently locked by another user",
and next thing you know, 3,4 or 5 others call with the
same lament. If everyone closes and reopens, all is well.
Found out it is happening when someone creates a record
and leaves the record in edit mode (pencil on left bar)
going off to do something else, then, another person will
try to add a record and get the error. Domino effect.

The way I see it, I have 2 options. 1. I can have each
user copy out the DB to their G drive each time I make
file edits so each is using a separate file. Downside here
is I have lots of folks that would just stare back and
ask, "Huh? What?" 2. I can have the forms 'time-out' and
close. This way, the DB is still open, they just need to
reopen the form they want. Seems like this is the best
option but don't know how to do this. It utilizes the
timer event procedure, but have never worked with it.

Could I get a few opinions and a bit of advice on what you
think? Would you mind giving me a little detail on how to
go about it or perhaps a website that addresses the issue?

Thanks in advance for any help and advice on this
conundrum. LUV U GUYS!!!

 

[Chris Reveille]

This informatio will be relevant...
http://support.microsoft.com/?id=128814

You can have a value stored in a table, that only the admin
has access to, and a hidden form on each desktop frontend
that uses to timer event to poll at regular intervals for
the value of this field. If you set it to a certain value,
a form will be displayed to the user advising them to close
the application.

Chris

 

[Orv]

This may help also
http://www.peterssoftware.com/isd.htm