OK, Working may have been a premature statement. It had all the appearances of working during testing but that was because I was doing inserts and it was being evaluated properly at the time.
I'm happy with my workaround and it works fine. Thanks for the discussion. Jan -----Original Message----- From: "MikeB" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 11 Mar 2010 18:28:07 -0500 Subject: [RBASE-L] - Re: TABLE Property - answered myself Well he hasn't said that the computed value is to remain static either. If it is to remain static and he is using #date in the computation, then the UPDATE command he issued changed all the values of the computed columns. Jim, he also said it "quit working" which wasn't maybe as concise as we (at least I) would have wanted to see. Even though it only works "when row is inserted or updated", it wasn't working at some point making me wonder about the integrity of the db. I'm with you on the VIEW. At least in my own db, I haven't seen the need for using a computed column for a verrrry loooong time. Any requirement for a computation can be done on the fly when needed. ----- Original Message ----- From: "James Bentley" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, March 11, 2010 6:05 PM Subject: [RBASE-L] - Re: TABLE Property - answered myself > To the best of my knowledge a computed column is evaluated only where the > row is inserted or updated. > Since Jan is using #DATE in the computed column, the computation will only > update with current date when row is inserted or updated. Hence until he > performs one of those actions the value of the computed column reflect the > #DATE value when one of those last actions was performed. > > A better approach might be to incorporate the computed column logic into a > VIEW and use the view to perform the needed actions. Executing the view > will also compute against the current #DATE. > > > Jim Bentley > American Celiac Society > [email protected] > tel: 1-504-737-3293 > > > > ----- Original Message ---- > From: MikeB <[email protected]> > To: RBASE-L Mailing List <[email protected]> > Sent: Thu, March 11, 2010 3:50:35 PM > Subject: [RBASE-L] - Re: TABLE Property - answered myself > > OK, but it still begs the ? of why it quit working. I would still do a > RELOAD. > > ----- Original Message ----- > From: "jan johansen" <[email protected]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Thursday, March 11, 2010 4:15 PM > Subject: [RBASE-L] - Re: TABLE Property - answered myself > > >> Group, >> >> Have the answer. I just forced an update and it worked >> >> --force sales table to revaluate >> UPDATE RunningSales SET SaleEnd = SaleEnd >> >> It worked fine. >> >> Jan >> >> >> >> >> >> -----Original Message----- >> From: "jan johansen" <[email protected]> >> To: [email protected] (RBASE-L Mailing List) >> Date: Thu, 11 Mar 2010 13:04:11 -0800 >> Subject: [RBASE-L] - TABLE Property >> >> >> Group, >> >> Using 7.6. >> >> I have a table that has a computed column to evaluate a date >> versus the current system date and update it's status. >> >> This process worked for some time and at some point quit. >> Is there a property command to force an entire table to re-evaluate >> itself? >> >> Jan >> > > > > >
