Custom Validation

[Phil Rolf]

I have the following line in the custom validation for the fields, Gamedate, Time, and Field_num. The code is to check for duplications of the three fields.

.NOT.KEY_EXIST("GameValid",CDATE(GameDATE)+TIME+STR(FIELD_NUM,4,0))

The code works fine during an enter. However, if I try and do a change of data, when I do a save F9, I get a FIELD VALUE NOT VALID error. Any ideas of what it will take to make this work?

Thanks

[Stan Mathews]

RE: Custom Validation

Try moving your expression from, I assume, a table level field rule, to a form level field event such as CanArrive.

Check the mode, change or enter, and if in enter mode, allow the entry, if in change mode, give focus to the next field in the tab order. Then do the same in the CanDepart, but now if in enter, perform the validation, if in change, just allow the change

Should work.

[Phil Rolf]

RE: Custom Validation

Stan,

I need the validation check in the change mode if they change any of the three fields in question: gamedate, time,field_num.

Currently if I enter a record and there is a duplication based upon the Gamedate index, I get a validation error (this is correct), I change the data (during the enter) that is causing the duplication and I can save the record.

If I come back to the record and try to change any field, not just the three for the validation rule, after I change data in a field and hit F9 is when I get the error.

You are correct, the code is currently stored in the table field rules for all three fields. I can put the code on only one field and the problem still exists.

[Tom Patten]

RE: Custom Validation

Try putting the validation code only on the last field to be entered (tab order). And if you "require" in field rules the other two rules so that they cannot get by them if they are blank. Then cross your fingers and give it a try...but I find the crossed fingers difficult to type with.

Good Luck

Tom

[Stan Mathews]

RE: Custom Validation

"If I come back to the record and try to change any field, not just the three for the validation rule, after I change data in a field and hit F9 is when I get the error."

I think that when the field rule fires from the table level field rules, on entry you are ok because either the key does not exist or it prevents you from creating a duplicate.

On the other hand, when you try to make a change anywhere in the record, and commit the change, the field rule fires again and now the key does exist......for this record. The key_exist function tells you if the index key value exists anywhere, not just in some other record.

[Finian Lennon]

RE: Custom Validation

This sounds just like the validation rule switch problem from 4.02 to 4.03 that is described in the readme403.pdf

You'll need to stop using key_exists and use key_unique instead.

Finian

[whanigsberg]

RE: Custom Validation

Phil:

(Stan, please check me on this.)

I believe you are hanging up on the difference between key_exist and key_unique which came in with version 4.03. Check page 31 of the 4.03 doc.

The change is that starting with 4.03 field rules are reevaluated on change. When you enter the record you are ok, but when you change it, the key already exists so your validation fails.

The documentation instructs you to substitute
key_unique(key_expression)
for
.not.key_exist(key_expression)

Bill

[Stan Mathews]

RE: Custom Validation

Bill,

You are correct. I found the reference to key_unique(), but Finnian got there first.

Thanks,

Stan

[Stan Mathews]

RE: Custom Validation

Wouldn't it be "nice" if Alpha redid the online documentation to reflect the current set of xbasic commands, instead of us having to search several documents to find the needed command?

[Phil Rolf]

RE: Custom Validation

Finian,

Thanks, I would have never found the new command without your message. I just changed the validation rule and the initial indication is that everything works fine with the key_unique command. In addition, the format is simpler.

Once again, thanks
Phil

[Barry Shadduck]

RE: Custom Validation

Thanks to all, especially to you Phillip for asking the question. I just fixed the same problem, but would like
to add (for the next poor slob unfortunate enough to
come across the same probelm) that the parameter list for the key_unique function does not include the key value,
only the reference to tagname (index) is needed.

Again thanks to all, said it before, and I'll say it again
without this forum, I'm dead.

With some 65 thousand hits on this thing (a5 forum) what can it mean ???? ..... hmmmmmm, maybe the pooorest documentation ever? Nah, just being facetious.