Unanswered: forms using recordsets / supressing autosave
Is there a way to supress the auto-save that occurs when a user moves from a parent form to a subform?
I am thinking of redesigning my forms as unbound, and running them off recordsets which I will use to populate the fields through code. Of course, I will also have to do my updates and inserts through SQL in the form code. Are there any drawbacks to doing this, such as performance or other issues? I am just getting tired of Access' auto-save behaviors, which are wreaking havoc on my attempts to run record validations (especially because the user needs to be able to navigate between parent- and sub-forms without these events being fired).