Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!rutgers!uwvax!ai.cs.wisc.edu!beverly
From: beverly@ai.cs.wisc.edu (Beverly Seavey (-Kung))
Newsgroups: comp.databases
Subject: more ORACLE SQL*FORMS gorey trigger problems
Message-ID: <11268@spool.cs.wisc.edu>
Date: 14 Sep 90 22:18:17 GMT
Sender: news@spool.cs.wisc.edu
Organization: U of Wisconsin CS Dept
Lines: 49


I am working with Oracle SQL*FORMS version 2.0. 


In one block-level KEY-ENTQRY trigger I have the following two
steps and they work just fine:


 1) #COPY &SYSTEM.CURRENT_FIELD GLOBAL.curr_aa;
 2) #EXEMACRO CALL &GLOBAL.curr_aa;


So the form that gets called at this point depends on the
value of the variable in GLOBAL.curr_aa. In this 2nd form
that gets called I have as a block level ( I also tried field
level) KEY-EXEQRY trigger the following 2 steps:


  1) #COPY &SYSTEM.CURRENT_FIELD GLOBAL.curr_atom;
  2) #EXEMACRO GOBLK molecule;
and the block MOLECULE has a key trigger :

     #EXEMACRO GOFLD &GLOBAL.curr_aa;


This trigger, which looks very similar to me, seems to be doomed on
two accounts:

   1) Oracle complains that the "&SYSTEM.CURRENT_FIELD" is an ambiguous

field name. It didn't find it ambiguous in the 1st situation. Both blocks being used have more than one column and for each I have the cursor positioned
correctly over the field of interest. If I remove the ampersand:

	  COPY SYSTEM.CURRENT_FIELD GLOBAL.curr_atom


Oracle no longer finds this ambiguous! Is the problem related to the fact
that I'm in a form called by another?????

Secondarily, I don't seem to be able to say

#EXEMACRO GOFLD &GLOBAL.curr_atom, although in the calling form
#EXEMACRO CALL  &GLOBAL.curr_aa; worked no problem.

 Is this problem a difference between how Oracle handles block names and
 form names ( and the corresponding GOFLDs and CALLs) or once again
 could it possibly have to do with nesting level?

 THanks for all the help so far.