Refresh Efficiency

[mjoachim]

Hello!

I currently have a continuous form and am using Me.Refresh as an After Update event for multiple controls on the form. Everything preforms great when there is a single user, but when multiple users are running their DB (back end is split out, each user has their own front end DB), performance becomes slow and choppy. (Bottleneck points appear to be at each refresh) I have already attempted to remove a few refresh points, but doing so made the user-friendliness of the app decrease. I have also gone through and added a few if statements in my code to try and eliminate unnecessary queries.

It seems like the problem is partially to blame on the entire form, sometimes up to 25 records, refreshing every time the Me.Refresh event occurs. Is there any way to update a single record on the form so that all other non active records are left alone?

Thanks!

[GKJR]

Is it really necessary to have the form refresh after the control values get updated? You could put a button in the header or footer that would refresh it when pushed. This way if someone is updating one of the records based on the other records displayed, they could refresh it to be sure nothing has changed since they opened it and then make their change. Access does record level locking so if one person is updating a record, no one else can change it until they're done anyway.

[mjoachim]

The form is actually being used for time entry, so the user isn't occasionally retrieving and updating records, but rather entering many records consecutively at approx 30-45 secs per record. I have thought about other ways to approach the refresh pattern, but I have totals in the form footer that are used to tie against the paper time card. I would like these form totals to remain as accurate as possible, which is why I have the record(form) refresh after update on each hours field.