Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!fernwood!oracle!news
From: tgreenla@oracle.uucp (Terry Greenlaw)
Newsgroups: comp.databases
Subject: Re: more ORACLE SQL*FORMS gorey trigger problems
Message-ID: <1990Sep17.212336.12568@oracle.com>
Date: 17 Sep 90 21:23:36 GMT
References: <11268@spool.cs.wisc.edu> <1990Sep17.200151.11764@oracle.com>
Reply-To: tgreenla@oracle.UUCP (Terry Greenlaw)
Organization: Oracle Corporation (Federal Division), Bethesda, MD
Lines: 27

In article <1990Sep17.200151.11764@oracle.com> I wrote
>It sounds like you have two fields with the same name on the form. To resolve
>the ambiguity do a #copy &SYSTEM.CURRENT_BLOCK || &SYSTEM.CURRENT_FIELD
>instead. Hope this helps your problem.
>
>tog

Sorry about the mungled (and obviously incorrect) answer. It should read:

#COPY &SYSTEM.CURRENT_BLOCK || '.' || &SYSTEM.CURRENT_FIELD ....
This will help SQL*Forms resolve which field you are talking about. The reason
your example worked for blocks is because their names are unique inside a form.
Ditto for calling forms. I just forgot to cat a period in there before.

I mentioned before about having a document which allows you to do pop-up
windows and pull-down menus in SQL*Forms ver 2.x. I can't find it in my
archives, so I will have to write it over from scratch. It really isn't hard
to do, but I want to make sure that the instructions I give will actually
work (see mangled message above), so it will have to wait until I get home 
for the weekend to try them out. I will also include a sample .inp file that
uses the technique as a template. Sorry about the delay,

tog
Terry O. Greenlaw             Sheathed within the Walkman, 
Staff Engineer                Wear a halo of distortion.
Oracle Corporation            Aural contraceptive,
tgreenla@oracle.oracle.com    Aborting pregnant conversation - Marillion