So the answer to this specific question posted above, was to keep the field bound, then setting the value of the bound <textfield1> to = 'null' at the start of the exit event. The query 'SELECT UserID FROM FormsData WHERE UserID = 'DDuck', would return nothing not 'null'. So by inference, setting the <textfield1> to 'null' before hand would ensure that the IF statement later on could evaluate if <textfield1> was null or returned something as != 'null'. This worked like a charm.
I don't however have a good sense on working with variables for Database calls and working in that space. The main reason is there are times where the Open, Save, Submit (push/pull) real time data bindings in the livecycle UI can be a mess, especially if there are multiples. Currently with multiple bindings and mixed types, I am getting an unusual error where:
I am not sure if this is a binding string issue or not. Curiously it commits this error to the last table column that I am attempting to bind. I like the idea of utilizing these standard bindings because, theoretically, they should be able to use the standard sourceSet.<DataConnection>.<SQL Functions, ie Addnew(), Delete(), First(), etc>. Makes the coding easy. But in practice, as it typical with LiveCycle Designer what should take an hour takes 14. At least for the inexperienced. We'll keep crack'a'lackin'.
Update:28MAY2019, Looking through, oh 10 year old blogs, I found this in the comments section of one of Stefan Cameron's blogs for a step back in time:
This is likely the explanation for why when I run app.alert(xfa.record.saveXML("pretty")); xfa.record.updatePassword node isn't represented, because I have another binding already loaded into the sourceSets model. See below.
I’m glad to hear you find useful things on my blog!
I believe the problems you’re experiencing are related to the fact that with bindings to database data connections, there can only be one record that is active at any given time. When you do the “addNew()” call, the data in the fields currently bound to nodes in the data connection is set into the current record and a new record is created.
While you can display multiple database records at once in a form, you can’t edit multiple records at the same time.
To do this, I would recommend you read my post on inserting, updating and deleting records in a database. Using this technique, you could have the user add and fill multiple rows in the table and then have a single submit button that they click when they’re done. The submit button’s script would then insert new records into the database, one for each row in the table.
<me> So, I guess I utilize the .clone() method and open() close() methods to interact with the specific fields on the submit button click. Brushing up on my SQL I am going to try to utilize some 'INSERT INTO SELECT' syntax and see if that gets me where I need to be.