Hi all,
I have MAJOR problems since the last patch. I've been reading about problems with deleting the last record in a table and I'm wondering if this is about that. I have many of the same scenerios in my database, and it seems they have all gone astray. I will describe one, and hopefuly get direction.
I have a Table and Form "Donations" for entry of charitable contributions into the "Donations" table. I enter the donations, each with a unique identifier for each donation and a batch identifier for the group of donations being entered (details unimportant). At completion of entering the batch group, I have an operation (button-based) that Appends the entire batch to a second table(DoPosted), and also modifies with the Date(), a field 'poststate" in each of the records in the batch within the transaction (Donations) table. Worked great!
I HAD a "catch" script called in the form Donation 'Exit' button, so that if the user hit this form 'EXIT" button without POSTING, it would 1) created the ~Variable: postcheck="", and 2) run the following script:
(a5_get_records_in_query("donations",s_quote((Var->postcheck))+" = Poststatus")= 0)
If .T., it would indicate the Post sequence had not processed and an error message would fire that "Posting had Not Occurred".
All was well until the last patch. Now, if I enter to Donations form accidentally or need to exit witout entries, regardless of the entry condition= "No aditional selection criteria", if I immediately hit the form Exit Button, even if the first Action on that button is 'Cancel', there is established a record in that table that fulfills the above criterion and generates the 'catch message' and hinders my progress.
What am I doing wrong?
Mike W
I have MAJOR problems since the last patch. I've been reading about problems with deleting the last record in a table and I'm wondering if this is about that. I have many of the same scenerios in my database, and it seems they have all gone astray. I will describe one, and hopefuly get direction.
I have a Table and Form "Donations" for entry of charitable contributions into the "Donations" table. I enter the donations, each with a unique identifier for each donation and a batch identifier for the group of donations being entered (details unimportant). At completion of entering the batch group, I have an operation (button-based) that Appends the entire batch to a second table(DoPosted), and also modifies with the Date(), a field 'poststate" in each of the records in the batch within the transaction (Donations) table. Worked great!
I HAD a "catch" script called in the form Donation 'Exit' button, so that if the user hit this form 'EXIT" button without POSTING, it would 1) created the ~Variable: postcheck="", and 2) run the following script:
(a5_get_records_in_query("donations",s_quote((Var->postcheck))+" = Poststatus")= 0)
If .T., it would indicate the Post sequence had not processed and an error message would fire that "Posting had Not Occurred".
All was well until the last patch. Now, if I enter to Donations form accidentally or need to exit witout entries, regardless of the entry condition= "No aditional selection criteria", if I immediately hit the form Exit Button, even if the first Action on that button is 'Cancel', there is established a record in that table that fulfills the above criterion and generates the 'catch message' and hinders my progress.
What am I doing wrong?
Mike W
Comment