Pop-up message to active users

[Mr-Re Man]

I have a database that is shared over the network with quite a few users.
Some are on email, some not. Occasionally, I have to access the system
quickly to make an adjustment/tweak or even udate reports through excel and
making numerous phone calls etc is frustrating.

I have found that if a user is in the database it will not let me save any
changes or refuse me from updating excel.

Is there a way to send a message through access to the users currently
logged on, informing them to quit the program?

....and if this is possible, if they have just got the access open behind the
scenes on their pc, it closes it down after 5 minutes for example.

tia

 

[BruceM]

There may be something of help here:
http://www.accessmvp.com/JConrad/accessjunkie/kickoff.html

 

[a a r o n _ k e m p f]

If your database is a pain in the butt-- them move to SQL Server

Question your premise:

a) if people won't get out when I ask them to
b) move to a DB that works even when people are doing things.

I use Access Data Projects-- and I can edit queries / tables, etc--
_WHILE_ people have their application open.
SQL supports multiple users-
Access was never designed- from the ground up- to support multiple
users.

Access isn't a real database, it has been obsolete for a decade.

-Aaron

 

[Klatuu]

First, ignore Arron Kempf. He is a know Troll who posts false information
and ususally denegrates Access.

The basic concept here is to use a form that is always open that has a Timer
Event running. If you have a form that now opens when you start your app,
add this new form hidden, and have it open the real start up form. The
form's timer should periodically check a table you have in the back end for
messages. When you want to send a message, you enter a value in a fiekd in
this table. When the form sees there is a message, it can pop up a Message
box notifying the user to log off. I would also include logic to give the
user a reasonable amount of time to logg off and if they have not, quit the
application.

 

[a a r o n _ k e m p f]

of course I talk shit about Access _AS_A_DATABASE_.

Access works great-- as a front end to SQL Server

anything else is ridiculously short-sighted