Event before moving to the next record on a form?

[June7]

If you don't want user to navigate with the navigation bar then disable it.



I don't know anyway to directly associate code with the navigation bar. Navigation will trigger the form OnCurrent event.

[Ruegen]

If you don't want user to navigate with the navigation bar then disable it.

I don't know anyway to directly associate code with the navigation bar. Navigation will trigger the form OnCurrent event.

even if I put a check for requirements before moving to next record on the current event the record will still move to the next one if the requirements functions are not met by the user of the form

so I can't prevent the user from moving to the next record.

[June7]

If this data validation is done on data entry to new record, navigation of existing records should not be an issue because an incomplete record will not be allowed.

[Ruegen]

If this data validation is done on data entry to new record, navigation of existing records should not be an issue because an incomplete record will not be allowed.

This is an edit form. If staff remove information they will be prompted to return it but when they close the form they will be forced to return data to the field.

however if they move to the next record I can't prevent them or force them to return data that.

[June7]

If user does edit data then the form BeforeUpdate event will trigger and that's where data validation code should be. The UPDATE and navigation should be canceled and user is forced to complete data entry. At least that is my understanding of form BeforeUpdate. I haven't actually used it in my project. Data entry/edit is by Single View form and validation code is behind button click event.

Could set fields as required in table and let Access nag. They will eventually get tired of being hand-slapped by Access and learn to finish data entry.

[Ruegen]

If user does edit data then the form BeforeUpdate event will trigger and that's where data validation code should be. The UPDATE and navigation should be canceled and user is forced to complete data entry. At least that is my understanding of form BeforeUpdate. I haven't actually used it in my project. Data entry/edit is by Single View form and validation code is behind button click event.

Could set fields as required in table and let Access nag. They will eventually get tired of being hand-slapped by Access and learn to finish data entry.

that's true but in our office sometimes the user might be organising something over a period of an hour and might not have the data on hand to complete the form when it nags, they might remove data and then come back later to complete the form then move to the next record.

They know the data is missing - for now.

However sometimes they forget after an hour has passed and move to the next record (or accidental click)

I'm surprised the office team didn't think about this type of situation - an unload next record event would be handy....

The only way I can think of covering for this is having my own record count & navigation buttons as controls instead of the bottom one.

[June7]

That's what I do. Didn't I mention that earlier?

[Ruegen]

That's what I do. Didn't I mention that earlier?

yup

*sadface*