BobyIsProgress
Member
Hi everyone,
I, on the usefull advice of @TomBascom , use the "DO FOR myTable TRANSACTION" every time I need to create, update or delete a row in tables.
But in one of my app I have an issue.
My code is write I follow:
MyTable1 will be the head of a buying request
MyTable2 will be the line of the buying request
I'm agree that the message box a the end was foolish of me.
My question is, inside of each procedure I wrote every creation transaction with "DO FOR .... TRANSACTION" but when I'm coming back to my triggers I still have locks on the different tables ? Did I miss something like a release statement or something ?
Thanks you in advance as always,
- BobyIsProgress -
I, on the usefull advice of @TomBascom , use the "DO FOR myTable TRANSACTION" every time I need to create, update or delete a row in tables.
But in one of my app I have an issue.
My code is write I follow:
MyTable1 will be the head of a buying request
MyTable2 will be the line of the buying request
Code:
My button choose trigger for create rows in many tables
Do some verification before starting the create procedure
RUN Procedure for create myTable1 row(input some data, output ROWID(myTAble1) ).
RUN Procedure for create myTable2 row (input some data, ROWID(myTAble1)).
MESSAGE "CREATE OK"
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END.
I'm agree that the message box a the end was foolish of me.
My question is, inside of each procedure I wrote every creation transaction with "DO FOR .... TRANSACTION" but when I'm coming back to my triggers I still have locks on the different tables ? Did I miss something like a release statement or something ?
Thanks you in advance as always,
- BobyIsProgress -