I am using calls to DAO objects for an Access database in a real-time environment
where I must be able to see when any updates happen and keep the user interface
up to date based on the updates. I communicate between the server and client
with winsockets to let the client know to update it's view from the database.
Unfortunately, the winsocket interface seems to be much faster than the
updates to the database and so the refresh upon winsock communication does
not reflect the real status. Is there a way to assure the data recorded
or updated to the database is flushed at a faster rate? Any suggestions
would be greatly appreciated.
Chuck Williams