Re: Commit-problem in forms / no data found question

There is only one commit statement in forms. When you call it after a coded DML, it will also commit any outstanding changes in the form. If there are no outstanding changes, you will probably also be seeing the message, "no changes to commit". I haven't done this myself, but I wonder if you can put [Quoted] your inserts and deletes into a stored procedure - in the database instead of in the form. Put the commit there instead of commit_form in the form, and just call the proc.

Question 2. Answer Yes. Exception when no_data_found then show-your-alert.

"Stefan Röhle" <roehle_at_mail.uni-mainz.de> wrote in message news:39D2FA69.BEF1FE2C_at_mail.uni-mainz.de...
> Hi there,
>
> I have constructed a form using form builder. My problem is that when I
> use SQL-commands like 'insert' or 'delete' they are not executed - only
> if I add 'commit_form' afterwards, but then the action is performed
> twice! Since I want to manipulate my data with SQL commands and not with
> the "build-on" functions I would like to know what to do in order to
> switch off the automatism so that a 'commit_form' command only executes
> my SQL commands.
>
> Second question:
> When no matching data is found, the message appears only in the 'status
> bar' in the lower left corner. I'd like an alert window to open when no
> data is found. Can this be done in the 'exception' section of pl/sql
> code? Or do I have to use a trigger?
>
> Thanks
>
> Stefan Röhle
>
> PS: Please answer via email as well because our news-server loses
> articles after a really short time...
Received on Thu Sep 28 2000 - 17:33:52 CEST