Re: Forms 3.0 Question

In article <glasstetter.3.000D6EA8_at_bmcwest.com>, glasstetter_at_bmcwest.com (Dan Glasstetter) writes:
|> I've developed a Budgeting application using Oracle 6.0/Forms 3.0 running on
|> DOS. This application will be used by 32 remote locations to develop budgets.
|> The users will be entering data, then modifying and "tweeking" the numbers
|> over the next several weeks to come up with a final budget.
|>
|> My problem is with the way that SQL*Forms handles field entry. The user must
|> either manually clear the field before entering new data, or I can clear
|> the field ON-NEW-FIELD-INSTANCE. The manual clear is a BIG hassle for the
|> user. The Auto clear is even worse, since as soon as the cursor enters a new
|> field, they no longer have any idea what the number was.
|>
|> I would like to simulate LOTUS's (or numerous other packages) data entry. In
|> these packages, the field will not clear until the user presses a data key.
|> This seems like such a simple task, yet I have not been able to come up with a
|> solution. I figure I'm in "tunnel vision" mode and missing the obvious. Can
|> someone please help ?
|>
|> Thanks,
have a non database field called "new number" or whatever, then after it is entered, you can use an on-validate-field or key-nxtfld trigger to update the database field. You could imagine other triggers as well, but the basic idea of having a non database field for the new number is the way that I would go with it.

|> Dan Glasstetter
|> BMC West Corp.
|> Boise, ID
|> glasstetter_at_bmcwest.com

Tom Orth
Argonne National Laboratory
orth_at_dublin.aps1.anl.gov
Speaking for myself Received on Thu Dec 09 1993 - 19:41:29 CET