nopposan Posted April 10, 2008 Posted April 10, 2008 I have a required "not empty" field that's there for data entry purposes. I'd like to leave the field validation that way but I'd also like to be able to run a script that inserts text into a different field. Right now, whenever I try to run my "InsertText" scripts I run into many error messages because of the "not empty" field being empty (no data entry yet). I know how to turn the error messages off with the SetErrorCapture[on] command, but that still leaves my script hanging and waiting for the now invisible "O.K." box to be checked before it will proceed to the next record. So, how do I turn off the validation and then turn it on again within the script? I may eventually have many validated fields and it could get really tedious having to go through each one and turn off the validation before running my script; not so tedious as clicking "O.K." 274 times though. : Cheers.
mr_vodka Posted April 10, 2008 Posted April 10, 2008 Hmmm well you can modify your field validations to validate by calcuation and then try have something like this: $$Override + NOT IsEmpty ( Self ) Then in your script, you can have your script include: Set Variable [ $$Override = 1 ] Do your other stuff... Set Variable [ $$Override = "" ]
nopposan Posted April 10, 2008 Author Posted April 10, 2008 Well, I think I get your gist. 'Tried a couple of things that didn't work though. (I think I should mention that this is a text field that I'm validating. It's also validated by the any data entered having to be a member of a list -- Yes/No/Unknown are the whole list.) Just to test the principle of this, I started with unchecking the "not empty" box and validating with the IsEmpty function. One thing I tried was to check "validate by calculation" and click on "specify" and then type in "not IsEmpty(Self)" That allowed the field to remain empty and the record to be committed without warning, however. I then tried "not IsEmpty (Self) = 1" But that also failed to insure that the field gets filled in. I'm a bit puzzled now. Thanks for the idea though. 'Seems like it might be the right kind of thing.
nopposan Posted April 14, 2008 Author Posted April 14, 2008 Well, that does seem to be a very direct approach! And, as Gomer Pile used to say, "Surprise, surprise." Wowee, it works. CommitRecords/Requests [skip data entry validation; no dialog] Golly gee, it was right under my nose! Thanks though. Much appreciated. :
Recommended Posts
This topic is 6068 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now