Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!xanth!mcnc!ece-csc!ncrcae!ncrlnk!uunet!mcvax!hp4nl!philmds!leo
From: leo@philmds.UUCP (Leo de Wit)
Newsgroups: comp.databases
Subject: Re: using triggers in pc oracle forms
Keywords: triggers help please
Message-ID: <952@philmds.UUCP>
Date: 12 Feb 89 13:38:15 GMT
References: <7606@xanth.cs.odu.edu>
Reply-To: leo@philmds.UUCP (Leo de Wit)
Organization: Philips I&E DTS Eindhoven
Lines: 24

In article <7606@xanth.cs.odu.edu> paterra@xanth.cs.odu.edu (Frank C. Paterra) writes:
|Hello Netlanders,
|
|I'm having a problem with sqlforms on the pc version of oracle.  Every
|things seems to work ok until I use a trigger that has a #EXEMACRO
|statement in it.  I've tried #exemacro exeqry, #exemacro nxtblk, and
|lots of others, but whenever it gets to the #exemacro statement
|I get the error "SQL error in processing post-field trigger".  I've tried
|using post-field, post-change, and pre-field triggers, but the result
|is the same.  

The problem is that you try to use exemacro on a non key type trigger
(I believe Oracle calls it 'synchronous trigger', or was it
asynchronous?).  With this type of trigger you can only use #exemacro
null (and some other seldom useful #exemacro's) or any userdefined
triggers that at most amount to this kind of exemacro stuff. If you use
a KEY-NXTFLD trigger instead and put the exemacro there, SQL*Forms will
be happy.

B.T.W. use the Display Error key (or whatever its name is) directly
after SQL*Forms reports an error; this might give you some indication
about the cause of the trouble.

	Leo.