Form Data entry Question

[Ray1127]

I have a form with a number of fields. There is a type field that depending on the type selected some fields are appropriate and others are not. I have all of that working. The problem is that if the user changes the type the non-appropriate fields are hidden but the data still exists. I want to validate so that when the type changes the user is given a warning and forced to remove the data from those fields. That all works the problem I'm having is that the type (a combobox) still changes How do I stop it from changing until all of the fields are blanked out?

 

[PWise]

on the before update of the type combo box do your checking and if wrong fields are filled

msgbox "wrong fields filled please edit"
cancel = true
exit sub

 

[dhookom]

Share your solution for "all of that working".

Duane
Hook'D on Access
MS Access MVP

 

[kjv1611]

As PWise suggested, you've probably got your code in the after_update event rather than before_update event. Swap that around, add in the cancel = true, and that part will be set.

What I'd wonder is would you rather just clear the fields automatically via code when the type is changed (and the user acknowledges the warning that the previous data will be erased?

It'd be more work up front, but the user would have less work to do, and they wouldn't have to look and make sure they cleared the correct fields.

 

[TheAceMan1]

How are ya Ray1127 . . .

[blue]What I'd wonder is would you rather just clear the fields automatically via code when the type is changed (and the user acknowledges the warning that the previous data will be erased?[/blue]

I could'nt agree more. Makes a much better interface!

See Ya! . . . . . .

Be sure to see faq219-2884 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[Ray1127]

Actually I couldn't agree more but my boss will not allow it. No clue as to why. He want's the user to have to clear it out.

It was in the before update event. But it's no longer relevant other priorities have put that DB on the back burner for at least a month. Thanks anyways.