Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!mit-eddie!uw-beaver!ubc-cs!alberta!myrias!aunro!apss!ncc!isagate!steve
From: steve@edm.isac.CA (Steve Hole)
Newsgroups: comp.databases
Subject: Re: need help with ORACLE SQL*FORMS
Message-ID: <1990Aug7.151057.20939@edm.isac.CA>
Date: 7 Aug 90 15:10:57 GMT
References: <10933@spool.cs.wisc.edu>
Reply-To: steve@isagate.nexus.ca (Steve Hole)
Organization: ISA Corporation
Lines: 35

In article <10933@spool.cs.wisc.edu> beverly@ai.cs.wisc.edu (Beverly Seavey (-Kung)) writes:
>
>
>   Why is it that whenever I have temporary fields on a form, whose
>   purpose is to gather information that will be used in later
>   queriesthat and  I can't subsequently call another form? I get the
>   message:
>
>	  Can't call form with changes to commit.
>


>   Inserting a commit into a trigger for these informational
>   fields doesn't help.

And really isn't something that you want to do.

>
>   Because the fields are strictly information gathering, they are
>   not directly associated with any tables, and were not created
>   using a table default.

But I suspect that they are database fields?  If so, you want to make
them non-database fields and the problem.  Somewhere in the block in
question, you are doing a #COPY into a database field, resulting in the
record being marked as 'updated'.   There are two ways to keep the
record from being marked.  Don't use #COPY (use field validation to copy
the value from another field), or make the field non-database.  The
trick to forms is organizing the form to still do what you want within
these restrictions.

-- 
Steve Hole  		         mail: steve@edm.isac.ca
ISA Corp.			 uucp: !{uunet, alberta}!ncc!isagate!steve
Edmonton, Alberta, Canada       phone: (403) 441-4121