Dawn: But I don't see the behavior you're explaining... The GETPROPERTY was in my field "on exit" eep, and it does pick up the correct value. If it was null before, and now it isn't null, thru tracing I can see that the getproperty retrieved my new not-null value into the variable. It gets to the code that changes the dbedit color based on the not-null value. So the getproperty is working even though the data isn't "saved" yet, it changes the color of the field (as I can see in the background as I trace), but then it reverts back as soon as it landed in the next field.
Maybe this is symantics, but I'd really like to know this -- if the field eep is "on exit", then you have left the field, right? You say it must be done "after you've left the field". But wouldn't an exit eep be evaluated after you've left the field? I don't think it's "as you are in the process of leaving the field"... Just wondering what your perception is compared to mine. Karen > The difference is, Albert in your example, you're selecting data from the > table. Karen is controlling the color based on data not yet saved to the > table. The only way to gather it is by setting a form variable, or using > GETPROPERTY. Using GETPROPERTY must be done AFTER you've left the field, so > it cannot be done in the on exit eep for that field, but rather in the on > entry eep for the next. >
