>It looks as if that, somehow, it "remembers" the original variable. (I'm not >saying R:Base does remember, only that it looks as if it is remembering - >there's a big difference.)
This jogged something in my memory with an app that David Blocker and I were working on. An eep would select data from a table into variables and do alot of processing. We needed to trap later on in the eep whether another user had made any changes to data in that other table since the time that the eep was started, so another select was done. Even if another user made changes while user#1 was still in the eep, the second select would usually (not always) bring up the original data. We asked RBTI why it was doing this, and were told that the old data was still in my cache so it grabbed it from there rather than going out to the table again. In order to 'force' the cache to be refreshed, we were told to do a bogus update to that table (like: Set TextCol = TextCol where record = <the record you're looking for>) right before that second select. Fixed the problem, but that always bothered me... I think the reason it didn't behave that way all the time is that sometimes the cache must have been flushed or filled up, or whatever, to cause it to lose that first select. Karen ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
