On 12 Feb 2002, at 22:18, A. Razzak Memon wrote: > It is hard to judge and see what else is involved to not > recalc the other variables. The best thing will be to > send me a sample privately, at mailto:[EMAIL PROTECTED] > with everything involved and let me take a look to see > what we can do to help you.
Thanks, I'll strip it down to something manageable. > Meanwhile: > > 01. Are you pre-defining those three "global" variables > with correct data types? Yup > 02. Is there any chance that those variables are being > re-defined with different data types? Nope > 03. Did the data type of any variable object located on > the form get re-defined after you located those > variables when you designed the form? They are defined at the top of the eep (same type)... I'll try removing that code. > 04. Did that thing "ever" work before? Nope.. but the one var that does work was done with work some weeks ago. The other two were being added. Thanks, Ben > > At 06:59 PM 2/12/02 -0000, you wrote: > >Razzak, > > > >Appreciate the explanation (and this fix will be helpful), but what I'm > >experiencing is a bit different... > > > >> if indeed it did change the value of a column or variable > >> in the current row ... > > > >There are three "global" variables placed on the form, unasocciated > >with either table (do not appear in "list variables", or on a row). An > >eep determines their value, and then recalc is issued. Only one of > >the three changes the display on the form. The other two only > >change when I click into the "other", or first, table. > > > >Thanks, > > > >Ben > > > > > > > >On 12 Feb 2002, at 20:42, A. Razzak Memon wrote: > > > >> > >> At 05:11 PM 2/12/02 -0000, Ben Petersen wrote: > >> > >> >Dr R>, > >> > > >> >Could you elaborate on how recalc var was repaired? > >> >I had noticed something similar a couple weeks ago, > >> >but it related (I thought) pretty specifically to > >> >look-up variables. > >> > > >> >Also, was recalc tab worked on in the process? > >> > >> > >> Ben, > >> > >> You want me to elaborate technically, or as an end-user > >> of The Glorious R:BASE 2000 (ver 6.5++), Build:1.851xRT03? > >> > >> I can tell you ALL about it as an end user. It will take > >> a long time to write about <g>. > >> > >> ----------- > >> Technically: > >> ----------- > >> > >> ... When a RECALC VAR command was processed in an EEP, > >> R:BASE did not flag the row as "dirty" when a value > >> changed (like when a column was set equal to a variable > >> that changed in the eep). We will now flag the row, as > >> well as any variable(s), "dirty" when using RECALC VAR > >> if indeed it did change the value of a column or variable > >> in the current row ... > >> > >> ---------- > >> In General: > >> ---------- > >> > >> Always STAY CURRENT with your versions. Some product > >> enhancements occur "under the covers"; they are built > >> into the engine and the user doesn't need to change > >> anything to take advantage of these enhancements other > >> than upgrade to the CURRENT version. Many of the > >> performance and optimization improvements of R:BASE > >> 2000 (ver 6.5++) for Windows fall into this category. > >> > >> Quite frankly, if you are using the CURRENT release version > >> of R:BASE 2000 (ver 6.5++), Build:1.851xRT03 and/or Oterro > >> (ver 2.5) and if you still find a bug in the latest build, > >> I recommend that you submit a formal request on R:DCC, > >> along with a sample database and associated command files, > >> and then watch the talented Dream Team work their magic! > >> > >> Ask those who have been enjoying the benefit of staying > >> CURRENT! > >> > >> The rest is history! > >> > >> Very Best Regards, > >> > >> Razzak. > > ===================================-============================ > Official R:BASE List Server: mailto:[EMAIL PROTECTED] > RBTI Events/Training: http://www.rbase2000.com/events > R:DCC Members: http://www.rbase2000.com/rdcc > ================================================================ > R:BASE, Oterro & R:Tango are registered trademarks of RBTI. > ==================================-============================= > > ================================================ > 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/ > ================================================ 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/
