janderscu
asked on
Access 2003 timeout?
I have an Access 2003 application that is used by out about 15 people that are often accessing the database simulataneously. I am getting complaints that one user is losing information that she is entering into a query datasheet. However this is consistent. Sometimes she re-opens and some of the data was not saved, and other times it is saved. The problem is hard to re-create but I was able to determine through questioning more that she does tend to leave Access open for long periods of time when she is not at her desk, so I think that it has to do with this. During periods of her inactivity, the query has been left open, but other users have accessed the same tables that the query references and somehow their changes override what she has entered. But I'm just not sure how Access handles this type of scenario. Does anyone have thoughts of how to address this? Some type of auto-timeout for the application that would close it out after some period of time? I have tried telling her she needs to get in, make her changes, and get out, but this is not happening so I need a fix from the software side. Thanks!
I'm with Pete.
As the developer, you can twist yourself into knots creating systems that attempt to protect users from themselves...
;-)
The key here is user education...
You may also wish to use forms for data entry, (not the "Query Datasheet"), so you have more control over users.
Finally, you can investigate all the different "Record Locking" strategies and settings in MS Access, but this is another topic.
;-)
JeffCoachman
As the developer, you can twist yourself into knots creating systems that attempt to protect users from themselves...
;-)
The key here is user education...
You may also wish to use forms for data entry, (not the "Query Datasheet"), so you have more control over users.
Finally, you can investigate all the different "Record Locking" strategies and settings in MS Access, but this is another topic.
;-)
JeffCoachman
ASKER
"You can build a ' period of inactivity' test into the application that closes the app after a certain time, or you could use a timer event in the form to close after a certain time"
How would you accomplish 'pediod of inactivity' test to close the app? I think I will look closer at this.
Also, I am planning to convert the entry to a form and set the query as the source so I agree with you Jeff that would offer more control. Assuming I did this , would the timer on the form make more sense than a totall close of the entire application?
How would you accomplish 'pediod of inactivity' test to close the app? I think I will look closer at this.
Also, I am planning to convert the entry to a form and set the query as the source so I agree with you Jeff that would offer more control. Assuming I did this , would the timer on the form make more sense than a totall close of the entire application?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The time out on the form I think is a good solution at this point and I will try this for a while to see if it is a reasonable work around. Thanks
How can software possibly know whether the user needs to save the record or not?
You can build a ' period of inactivity' test into the application that closes the app after a certain time, or you could use a timer event in the form to close after a certain time, but it would be entirely a matter of chance in deciding whether you should be saving any unsaved data at that point. And what if some validation rule fails if you attempt to save?