Jim, A column defined with an expression has never calculated until the row was saved. If you had a form or process where you saw that value before that, then either an expression was used in the form to set a variable to the identical calculation, or a "save" was executed earlier through an EEP to refresh the value.
Bill On Mon, Mar 30, 2009 at 11:16 AM, Jim Belisle <[email protected]> wrote: > Larry, > > > > If I understand what you are saying, I do not think that is the case. > Below is the way the detail temp table is created. > > > > CREATE TEMPORARY TABLE `tQuoteDetail2` + > > (`QuoteID` TEXT (11), + > > `ItemNum` INTEGER, + > > `Model#` TEXT (20), + > > `ProdDesc` TEXT (80), + > > `Quantity` REAL, + > > `ModelExtWgt` REAL, + > > `KPRSell` CURRENCY, + > > `Discount` REAL, + > > `ItemPrice` = (KPRSell-(KPRSell*Discount/100)) CURRENCY, + > > `ItemExtPrice` = (Quantity*ItemPrice) CURRENCY, + > > `PalletExtCharge` CURRENCY) > > > > For some reason, the ItemExtPrice is now not calculating until I leave the > row. It worked just fine before the new column was added. > > It is the variables in the header area that are not calculating and they > were before. The only thing changed is the added column and the variables > associated with the column. > > > > Since this information is in a scrolling region, was I supposed to delete > the scrolling region before adding the extra column? > > > > jim > > > ------------------------------ > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Lawrence > Lustig > *Sent:* Monday, March 30, 2009 9:49 AM > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - Re: Basic question > > > > << > > I have a quote form that I have added one column to. This form is based on > temporary tables. I was able to add the columns with no problem. I have an > EEP that runs on exit from the Quantity field. Prior to adding the new > column, it worked in the same row immediately on exiting the field. Now I > have to go to the next row and key through the quantity field before it > triggers. I have shown the EEP from before and after adding the new column. > > >> > > > > At a guess, here's what happened: > > > > Previously, your field with the EEP was the last located field for that > row. The new field you added is located after the field with the EEP. Now, > when the EEP executes, the current row has not yet been written to the > actual database, so that the SELECT statement is not satisified. > > > > You can address this issue by adding SAVEROW to the beginning of your EEP. > > -- > > Larry > > >
