Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bg0l+
From: bg0l+@andrew.cmu.edu (Bruce E. Golightly)
Newsgroups: comp.databases
Subject: Re: resuming to a new field in form.
Message-ID: <0Ywdlvy00WB7Q1l6BZ@andrew.cmu.edu>
Date: 23 Aug 89 12:45:47 GMT
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 15

The comments made by Mr. Fair are certainly true. Both QUEL and SQL provide
mechanisms for controlling movement from field to field. These do not work
in the most useful fashion under certain circumstances.

Under Ingres V5, RESUME causes a RETRIEVE or SELECT loop to terminate. The
developer must, therefore, choose between the use of a select loop (with
its sub-menu) and the contorl provided by resume. This can get very interesting
if cursor movement has been attached to an FRSKey definition within the
current block of code. (This subject formed the basis for a paper I did
at the national conference in New Orleans last April.)

I don't have the release 6 doc handy, so I will refrain from comment on that.
It does stick in my mind that this one was on the hit list, though.

Bruce