J
John Thomas
In 97 multiuser database, I am attempting to create a
simple messaging system that alerts users to exit the
database. Here's my setup:
1. I fill in a text box with a message to all users.
2. Command button inserts a row into my messages table.
3. My main menu (which is ALWAYS open, regardless of what
form or report user is in) has its TimerInterval set to 5
minutes. The OnTimer event should fire every 5 minutes
for every user.
4. The OnTimer event checks the messages table for a
record, containing my message (this table is otherwise
empty).
5. If a message is detected, the code opens a form and
populates a text box with my message.
6. When the user clicks my close button, it deletes the
message from the messages table.
7. I use a listbox populated by a borrowed function that
pulls connected users from the ldb file, and can see them
disappear as they exit the database.
Problem: The message form does not appear for all users.
Users in another part of the building never see it, while
users nearby do see it (not that a user's proximity is the
cause). I know these users are not manually closing the
main menu (I've tested it).
My question: Is there a better approach to this kind of
technique? I know this kind of thing has been designed
before, and perhaps with much better success.
Caveat: I'd also like the option of a forced shutdown,
which will automatically exit Access without any user
input.
simple messaging system that alerts users to exit the
database. Here's my setup:
1. I fill in a text box with a message to all users.
2. Command button inserts a row into my messages table.
3. My main menu (which is ALWAYS open, regardless of what
form or report user is in) has its TimerInterval set to 5
minutes. The OnTimer event should fire every 5 minutes
for every user.
4. The OnTimer event checks the messages table for a
record, containing my message (this table is otherwise
empty).
5. If a message is detected, the code opens a form and
populates a text box with my message.
6. When the user clicks my close button, it deletes the
message from the messages table.
7. I use a listbox populated by a borrowed function that
pulls connected users from the ldb file, and can see them
disappear as they exit the database.
Problem: The message form does not appear for all users.
Users in another part of the building never see it, while
users nearby do see it (not that a user's proximity is the
cause). I know these users are not manually closing the
main menu (I've tested it).
My question: Is there a better approach to this kind of
technique? I know this kind of thing has been designed
before, and perhaps with much better success.
Caveat: I'd also like the option of a forced shutdown,
which will automatically exit Access without any user
input.