Jason said:
if checking itself then it is checking form. I'll check if subform remains
dirty after going back to main form to make sure of this before I print the
report.
I already have that command on the parent form for checking itself. The
caommand buton is on the parent form but if I haven't gone from editing
current record in the subform to either a new record or another record then
I would have thought dirty = true.
Going from the subform to the main form should save any
changes the same as going to a different record in the
subform.
The situation that I am unsure of is when a VBA procedure in
the main form sets values in the subform. Clearly this
would make the subform dirty without a save, but if/when the
modified subform record is saved is unclear unless the main
form procedure explicitly does it.