Are you saying that if the Agent called from line 1 of the @Formula in the Form's WebQuerySave Event fails for any reason then the second line of the formula (the @SetField) won't be called?
In this scenario does the document itself get committed to the database at all?
Another idea I had was to set SaveOptions field to "0" on the form submitted and only change it to "1" at the end of the Java agent (after the ccnumber field was removed).
I concur entirely with your approach to not storing CC data. But I'm between a rock and a hard place. You wouldn't believe what a beast of a system the previous developer had come up with. Turning off the "generate all field" option is what I want to do. I just daren't do it.
Are you saying that if the Agent called from line 1 of the @Formula in the Form's WebQuerySave Event fails for any reason then the second line of the formula (the @SetField) won't be called?
In this scenario does the document itself get committed to the database at all?
Another idea I had was to set SaveOptions field to "0" on the form submitted and only change it to "1" at the end of the Java agent (after the ccnumber field was removed).
I concur entirely with your approach to not storing CC data. But I'm between a rock and a hard place. You wouldn't believe what a beast of a system the previous developer had come up with. Turning off the "generate all field" option is what I want to do. I just daren't do it.