Has anybody tried to customize assignDBRow in your SDO?
I want to completely DISCONNECT progress default when add, copy and update record in my table.
I have my own MyCreateRecord.p
But I want to use Progress toolbar for view and update viewers/ browsers.
I do as follows in my SDO
PROCEDURE assignDBRow:
DEFINE INPUT PARAMETER phRowObjUpd AS HANDLE NO-UNDO.
/* Code placed here will execute PRIOR to standard behavior. */
RUN MyCreateRecord.p.
/* RUN SUPER( INPUT phRowObjUpd). */
/* Code placed here will execute AFTER standard behavior. */
END PROCEDURE.
It seems to works with copy and update, but not very well with add. Progress ADM2 goes out of sync and I get progress errors because I commented out the RUN SUPER.
OK... so I tried to put my RUN MyCreateRecord.p. in pre/ begin/ endTransactionValidate with a RETURN "Message".
But the undo transaction will also back out the work MyCreateRecord.p does.
Any suggestion were to put my code is highly preciated.
(ADM2 or not is the question)
I want to completely DISCONNECT progress default when add, copy and update record in my table.
I have my own MyCreateRecord.p
But I want to use Progress toolbar for view and update viewers/ browsers.
I do as follows in my SDO
PROCEDURE assignDBRow:
DEFINE INPUT PARAMETER phRowObjUpd AS HANDLE NO-UNDO.
/* Code placed here will execute PRIOR to standard behavior. */
RUN MyCreateRecord.p.
/* RUN SUPER( INPUT phRowObjUpd). */
/* Code placed here will execute AFTER standard behavior. */
END PROCEDURE.
It seems to works with copy and update, but not very well with add. Progress ADM2 goes out of sync and I get progress errors because I commented out the RUN SUPER.
OK... so I tried to put my RUN MyCreateRecord.p. in pre/ begin/ endTransactionValidate with a RETURN "Message".
But the undo transaction will also back out the work MyCreateRecord.p does.
Any suggestion were to put my code is highly preciated.
(ADM2 or not is the question)