vb code in a form's properties for a single field -Limitations?

  • Thread starter Thread starter Cagey
  • Start date Start date
C

Cagey

Is there a rule in vb that limits the # of Properties I can put into
code for a single field? (e.g. Lost Focus/Got
Focus/OnCurrent/Dirty/OnChange/AfterUpdate, etc.)
 
Assuming you're talking about events rather than properties, the answer is
no. If you're talking about properties, the answer is still no. In fact, all
answers today are No.

Barry
 
Barry said:
Assuming you're talking about events rather than properties, the answer is
no. If you're talking about properties, the answer is still no. In fact, all
answers today are No.

Barry
a user clicks on that field & when the click means the user will be
making a different selection from that
dropdown list(a), EXCEPT when other fields have not been updated. This
is difficult because several of the
other fields have a programmed prefix in the field according to the
dropdown list(a) choice selected. So, my
thought was to write vb code to do this & let the warning message occur
for (a) when a required field(b) is empty.
Part of the issue w/that, is that (b) field occurs on the form after
other fields that follow(a).

Hope this is clear. Any suggestions on how to do this? If possible,
I'd prefer the user didn't have to say ok to every
message/warning I have set, but just continue & the message would go
away. (Probably due to faulty set up on my
part, the warning msg I'm referring to appears at some unnecessary
times & every time it does, certain fields are
wiped out, if not immediately then as soon as those certain fields are
clicked or entered into).
 
Back
Top