Unbound Recordsets

What is the most efficient way to keep client data current in a network using unbound ADO recordsets from VB 6.
The program started out as a single user, but has quickly evolved to a network. The front end is VB6 while the backend is a MSAccess 2000 mde.
The system runs great, but if a user has been idle for a period, the users data is not current.
I thought about writing a procedure that would automatically update all users when an entry was made into the database, but that does not seem real efficient.
I also thought about adding a 5 second timer to user systems, but since I work with scheduling systems, I fear that an update could knock out a schedule as its being entered.
A reminder, none of my forms etc are bound to a data control. The majority of updates etc is purely SQL. conn.execute