PROBLEM WITH 'COMMIT' COMMAND IN FORM 4.5

Question

During any process if I use COMMIT command after insert, update
or delete command in table which is not the base table of
current form a message appears on screen 'No changes to save'
and changes are saved in the table. How can I stop this message?
If I use Database trigger then I am not sure if I would be able
to use Rollback command.
null

Answer 1

If you are referencing standard.commit, it works for me. I
am using v4.5, I am assuming if is the same for 5.0 or 6.0 if 5.0
or 6.0 is your product.
Having said that all solutions mentioned are valid. I would
recommend next to try:
v_system_message_level := :system.message_level;
:system.message_level := '5';
commit;
:system.message_level := v_system_message_level;
If you modify the on-error/message trigger you may not
receive this error when it is raised when you really
do want to see it.
Faisal Shaikh (guest) wrote:
: No it didn't work any other ideas
: steve (guest) wrote:
: : Try using STANDARD.COMMIT;
: : Faisal Shaikh (guest) wrote:
: : : During any process if I use COMMIT command after insert,
: update
: : : or delete command in table which is not the base table of
: : : current form a message appears on screen 'No changes to
: save'
: : : and changes are saved in the table. How can I stop this
: : message?
: : : If I use Database trigger then I am not sure if I would be
: able
: : : to use Rollback command.
null