Can't cancel() in the CanWrite event of a field.

[CALocklin]

The Help text says, "All of the events whose names are prefixed with "Can" can be canceled, thus preventing the event from occurring."

However, when I use Cancel() in the CanWrite event of the field rules it still writes everything I typed. For example, I have a Company_Name field with a CanWrite field event that is simply Cancel(), any edits I make in the field remain after I leave the field. The only noticeable difference is that when I tab out of the field I have to hit the Tab key twice (or hit Enter twice or click in the next field twice).

This makes the cancel() command rather useless in this case. I'm pretty sure this used to work in earlier versions.

Can anyone else confirm this - or tell me what I have to change to make it work?

[Stan Mathews]

Re: Can't cancel() in the CanWrite event of a field.

CAL,


Confirmed by inserting a debug() before the cancel(). Nothing is cancelled even though the line is executed.

I think you can accomplish the same thing with

tbl = table.current()
A_FIELD_VALUE.Value = tbl.fieldname 'fieldname you want to cancel the canwritefield event.

[CALocklin]

Re: Can't cancel() in the CanWrite event of a field.

Thanks for the confirmation Stan. I had used debug() to confirm it was running, too. I wanted someone else to confirmation it in case it was something I did elsewhere that I was missing. My workaround was close but not close enough. Yours did the job.

And we now have another workaround for something that previously worked but is now busticated. I'd report it as a bug but my history on bug fixes isn't very good.

For anyone wondering why I would put just a "Cancel()" in the CanWrite field rule, I only did that for testing purposes. This is a password issue and I don't want any changes unless the user is in a particular form with the appropriate password entered in a variable on that form. In particular, only users who have the Superuser password should be allowed to change the Master password. I know that some users know how to get into the raw data so I don't want them to be able to change it there. (And all passwords are saved in encrypted format so they can't read them unless they are in the form and have at least the master password.) So the field rule in the table says "Cancel if there is no parent form or the parent form is not the correct one." The form's CanArrive event tests for the Superuser password and warns the user if they attempt to enter the field without entering the correct password first. The form rule would be enough if I didn't have to worry about someone getting into the raw data.