you can either use a calculated validity check (if field1 is set, not entry is valid in field2), or if you want to disable completely the ability to enter the field, use the example "Feld Unsichtbar / sichtbar"...
http://fmp.haifischbar.com:88/downloads/Default.aspxin the case of "visible" you could set the field with editing enabled, in tha case of "invisible" you could set editing disabled.
if you like my example, make a donation to a wellfare organisation of your choice, and proof it in my database ;-)
greetings from germany
Hmm, dont get it. Is not entry a function? I do not wish to look at the example to download the example, as there are strings attached.
Sorry I guess I should read your entire post before attempting to provide you with a solution ...
This is more of what your looking for:
OnObjectEnter for Insurance List Field:
If [YourTable::Payment Type Field = "Client"]
Set Field [YourTable::Insurance List Field; ""]
OnObjectEnter for Client List Field:
If [YourTable::Payment Type Field = "Group"]
Set Field [YourTable::Client List Field; ""]
Basically this will check if your "Payment Type" field is set to "Client", if so... then set "Insurance List Field" to an empty string ( thats if this field is text of course)
Or if the "Payment Type" field set to "Group", then set the "Client List Field" to an empty string ( thats if this field is a text field too)
Now thats what i'm talking about, THANKS!
SCOPe, I dont have time right now to to try it out, (heading to work) but I will give it a shot tonight!
One note, the two " fields "Client List" and "Insurance List" are set as a pop-up menu and are foreign key fields in a relationship. I don't think this conflicts with the script?
No it shouldn't conflict with the script, now that I look at it though. Instead of using OnObjectEnter, I would use OnObjectExit instead. Let me know how it works~