Timer To Shut down database when idle

[Lamont via AccessMonster.com]

I have a database that I've just took over. It has timer code to shut down
the database if when on the main form , it is idle for 5 minutes.

The problem that I'm having is that this is a network database, and everytime
the database shuts down this way while other people are in it, it causes
Access to lock up. It prevents others from going back into it and prompts to
repair the database. But when you click "yes" to repair, it says that you do
not have exclusive access to repair the database. However, no one is in the
database. The only thing that clears it up is the nightly refresh of the
network drives.

Does anyone have a solution to prevent the lockout?

Thanks,
Lamont

 

[Albert D.Kallal]

Are you talking about a multi-user application here?

IF you have a multi-user application, then read the following as to how to
set this up:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Douglas J Steele]

Do you have each user accessing the same database? That's not a good idea.

Your application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relationships). Only the back-end should be on the server: each
user should have his/her own copy of the front-end, preferably on their hard
drive (as opposed to on a network drive)

 

[JethroUK©]

i have a split my database front and back end - i am creating some front
ends for other staff - i understand that any particular record will be
locked during editing by any front end - but am i right in thinking they
will be able to share the back end tables without setting any special
sharing permissions?

Do you have each user accessing the same database? That's not a good idea.

Your application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables and relationships). Only the back-end should be on the server: each
user should have his/her own copy of the front-end, preferably on their hard
drive (as opposed to on a network drive)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I have a database that I've just took over. It has timer code to shut down
the database if when on the main form , it is idle for 5 minutes.

The problem that I'm having is that this is a network database, and everytime
the database shuts down this way while other people are in it, it causes
Access to lock up. It prevents others from going back into it and

prompts

to
repair the database. But when you click "yes" to repair, it says that

you

 

[Douglas J Steele]

As long as all users have Change access (Read, Write, Delete and eXecute) to
the folder where the back-end database exists, you should have no problems.
(In case it isn't apparent, I'm talking NTFS permissions on the folder:
nothing to do with Access permissions)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

i have a split my database front and back end - i am creating some front
ends for other staff - i understand that any particular record will be
locked during editing by any front end - but am i right in thinking they
will be able to share the back end tables without setting any special
sharing permissions?

 

[JethroUK©]

As long as all users have Change access (Read, Write, Delete and eXecute) to
the folder where the back-end database exists, you should have no problems.
(In case it isn't apparent, I'm talking NTFS permissions on the folder:
nothing to do with Access permissions)

I understand the windows permissions bit (the company have heirachy of
network permissions already setup) and all staff have read/write to the back
end folder - just the Access table sharing i wasn't sure about - thanks very
much