-
Hi there. I've made up a program in which each time a textbox is 'validated', it stores the new value in the current recordset. Each time such a modification is made, I'm calling a function that triggers .edit on the recordset. I DO NOT UPDATE right after. This only hapens when the user clicks on the "SAVE RECORD" button.
Will triggering .edit many time on the same recordset affect the memory usage, or will it affect the speed of my application? I solution to this might be, before triggering the .edit, to check if the recordset is already in 'edit' mode. How can this be done?
Thanks!
-
Actually this was a pretty stupid question. Sorry for this. :|
Triggering the second .edit will make you lose your first modifications to the recordset.
I'm thinking about using the recordsetclone. My other question: is using .edit straight on the recordsetclone affecting the original recordset? Because I want to keep track of all the modifications done to the fiels and if the user wants to cancel these changes, I want to take the values in another recordset and set them back correctly.
Then I'd have to declare explicitely another recordset containing this clone.
...comments, etc. =)
