Timer To Shut down database when idle

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Lamont - 30 Jan 2006 23:55 GMT

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

Reply to this Message

Albert D.Kallal - 31 Jan 2006 11:48 GMT

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

Signature

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

Reply to this Message

Douglas J Steele - 31 Jan 2006 11:48 GMT

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)

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(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.
[quoted text clipped - 11 lines]
> Thanks,
> Lamont

Reply to this Message

JethroUK© - 31 Jan 2006 21:45 GMT

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.
>
[quoted text clipped - 33 lines]
> > Message posted via AccessMonster.com
> > http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200601/1

Reply to this Message

Douglas J Steele - 01 Feb 2006 20:18 GMT

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)

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(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
[quoted text clipped - 42 lines]
> > > --
> > > Message posted via AccessMonster.com

http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200601/1

Reply to this Message

> 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

> --
> Doug Steele, Microsoft Access MVP
[quoted text clipped - 55 lines]
> > > >
> http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200601/1

Reply to this Message