Bound Columns: Are they a drain on network traffic?

[hellind]

I have a form bounded to a table in a back-end MDB.

The OnTimer is set to auto save every 5 minutes.

Question: How fast does an update in the form gets saved in the database table?

I've tested that it is saved instantly: I make a change and quickly exit access, and when I reopen the update is already saved.

Are there any controls for me to reduce the speed of update? I have 20 users connecting to the back-end from their respective front-end and I feel it is a drain on network performance.

 

[Galaxiom]

Changes are saved as soon as the user moves to another record or the form is closed. The traffic in an update only transmits the changed record not a whole table of records like in a spreadsheet.

You are worrying unnecessarily.

 

[gemma-the-husky]

out of interest, what access ACTUALLY does when it saves a record (in the default - no locking - mechanism) is this.

if you changed the record, it needs to save it -
so it re-reads the record to see if the record is the same as it was BEFORE your changes
if it hasnt changed it saves your data
if (unusually) it HAS changed - then you get the "another user changed your data" message, and you cant save your changes - so you are protected against "random" updates

because of this, you can accidentally cause this problem yourself. if you have a record open, and then open another form based on the same table - you can cause exactyl this effect

the downside of this automatic saving is (unlike excel) there is no undo feature once the record is saved/committed