G
Guest
I've got a form that views single records in a table, and the navigation
buttons are turned off. There's a subform with a datasheet view of a related
table, where there can be several records associated with the one record in
the main form.
The main table has a "last updated" field, and I've set the form up so that
when the user clicks on the OK button, if the form is dirty, the last updated
field is filled in before the form closes. I want to be able to do the same
thing if any records have been added or delete from the subform.
I finally figured out (I think) how to check to see if the subform is dirty.
I added the code, but the last updated field wasn't getting filled
in/modified, so I thought I was doing something wrong. After thinking about
it for a while, I realized that it was probably working fine, it was just
that the subform wasn't actually dirty by the time the OK button was being
clicked, as the new record had already been written into the associated table.
I have to guess that this isn't a bizarre scenario, and that there's
probably some standard way of dealing with it. If anyone can shove me in the
right direction, I'd appreciate it.
Thanks,
Rich
buttons are turned off. There's a subform with a datasheet view of a related
table, where there can be several records associated with the one record in
the main form.
The main table has a "last updated" field, and I've set the form up so that
when the user clicks on the OK button, if the form is dirty, the last updated
field is filled in before the form closes. I want to be able to do the same
thing if any records have been added or delete from the subform.
I finally figured out (I think) how to check to see if the subform is dirty.
I added the code, but the last updated field wasn't getting filled
in/modified, so I thought I was doing something wrong. After thinking about
it for a while, I realized that it was probably working fine, it was just
that the subform wasn't actually dirty by the time the OK button was being
clicked, as the new record had already been written into the associated table.
I have to guess that this isn't a bizarre scenario, and that there's
probably some standard way of dealing with it. If anyone can shove me in the
right direction, I'd appreciate it.
Thanks,
Rich