Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!cs.utexas.edu!uunet!mcvax!unido!radig!peter From: peter@radig.UUCP (Peter Radig) Newsgroups: comp.databases Subject: Re: Question about Oracle SQL*Forms Keywords: oracle forms master detail Message-ID: <753@radig.UUCP> Date: 14 Jun 89 06:27:54 GMT References: Reply-To: peter@radig.UUCP (0000-Peter Radig) Distribution: comp Organization: Peter Radig, Frankfurt, West Germany Lines: 45 In article lawhorn@optis31.uucp (Jeff Lawhorn) writes: >We have recently started using SQL*Forms. Now I have a question > >I have 2 tables that I need to establish a master/detail >relationship between. [stuff deleted] >I do not (can not) >want the user to have to switch blocks to call up the detail >records. Thats a quite nasty job to do and I think it's one of the most unsatisfying solutions in the ORACLE system. You have to redefine several Key-Triggers with the major objective of going into the detail block and retrieving the data whenever a new master block is displayed. So define in Master block: KEY-ENTQRY: #exemacro clrblk; goblk detail; clrblk; goblk master; entqry; goblk detail; exeqry; goblk master; KEY-EXEQRY: #exemacro exeqry; goblk detail; exeqry; goblk master; KEY-NXTREC: #exemacro nxtrec; goblk detail; clrblk; exeqry; goblk master; KEY-PRVREC: #exemacro prvrec; goblk detail; clrblk; exeqry; goblk master; Some information is provided by ORACLE in the SQL*Forms Release Notes Version 2.0 on page 48 (I definitely do not know why they put it under the Errata...). I hope with this information you're able to create your forms, don't hesitate to e-mail. -- Peter Radig Voice: +49 69 746972 USENET: peter@radig.UUCP or: uunet!mcvax!unido!radig!peter