Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!daver!kcdev!genco!rad
From: rad@genco.uucp (Bob Daniel)
Newsgroups: comp.databases
Subject: Re: Oracle SQL*FORMS 3.0 and SQL*MENU 5.0 gripe
Message-ID: <42@genco.uucp>
Date: 17 Sep 90 23:44:32 GMT
References: <2357@ns-mx.uiowa.edu>
Reply-To: rad@genco. (Bob Daniel)
Distribution: usa
Organization: Gentry & Assoc. Excelsior Springs, MO
Lines: 26


The folowing comments are based on Forms 3.0.14 for UNIX.  We have been a
beta site since Jan '90 and have been using the production release version
for over a month.

In article <2357@ns-mx.uiowa.edu> broy@vaxa.weeg.uiowa.edu writes:
>
>	Specifically, the master-detail block triggers are not created for
>more than one detail block. And if you try to delete blocks and then recreate
>them, you can't generate the form.

You can create master-detail block triggers on more than one block by first
creating the master block.  Then for each detail block, use 'default' and
tie in your master block.  This will allow more than one detail block.  AS
far as deleting a block, you must create it as a 'default' block to get
your triggers back.  I don't think it's a bug.. just the nature of Forms 3.0.

>in the table it causes nothing but problems. The interface between menus and
>forms is a real mystery. The manuals barely address this feature and Oracle
>Support is usually expert at one product or the other - not the combination.
>Many of the MENU commands don't work if linked to FORMS. 


SQL Menus apparently has problems.  They aren't even going to release for
UNIX last I heard.  We are bummin bad cause our application was going to
take major advantage of menus... At least you have it. :)