Re: 1 More Question, I Swear...Action Listener For Changing
I was looking at this one and now think the Validation Rule property is the best route to go. A value you can throw into it is:
Is Not Null
Exactly like that, with spaces, but you put it in the underlying table that the form is based upon. I haven't checked whether the exact same property is available for a textbox but it probably is.
The only thing I noticed when using this is that I didn't get an error message even though I entered/exited the field until I attempted to preform an action based on the contents of that field (completely unrelated to your question)
You'll get an error message that must be fixed, but you won't get it until well after the user leaves the field. My experience with forms is limited, but I believe that you should be able to force the field to test it's validation rule based on an Event such as OnExit (Exit) although I haven't tested this.
The OnExit property help text says:
"The Exit event occurs just before a control loses the focus to another control on the same form. "
and
"The Enter and Exit events apply only to controls on a form, not controls on a report."
One other thing you can try is this.
From the Form Design mode, you can right-click a control and select properties. If you then go to the Event tab, it should give you the names of all the events that are applicable to this control at this time. It doesn't explain what they do/how they work/when they work - but it's still a clue.
Something else you can do is use the object browser from within VBA to look at the various properties associated to everything. Really this part is intended to show you how to do it in VBA, but it could still help.
I hope this moves you closer to your goal.
Mike