I have a slightly different question related to this subject: I have a scrolling region with DBEdits and DBVars.
Some of the values for the variables may not exist until another form is opened and data entered. I then have to go back to each affected row and make a minor change to force R:Base to look-up the variables. I have tried an "On Row Entry" eep that does a ReCalc Vars but that seems to put R:Base into a loop which crashes pretty quickly. What is the correct way to force R:Base to re-evaluate a row in a scrolling region without actually making a change? Thanks & regards, Alastair. ----- Original Message ----- From: "A. Razzak Memon" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, August 26, 2004 5:31 PM Subject: [RBG7-L] - Re: Edit From > At 11:59 AM 8/26/2004 -0400, you wrote: > > >I have an office button that fires a save row and exit. It does > >not save the row because R:BASE does not detect that there is a > >change to and of the field information. > > > John, > > 01. After changing the value, make sure to either press [Enter] > key or [Tab] key and then click on the Office Button. > > OR > > 02. Use the "Custom EEP" for Office Button with the following > commands: > > RECALC VARIABLES > CLOSEWINDOW > RETURN > > Hope that helps! > > Very Best R:egards, > > Razzak. >
