Thanks Ben, and everyone else that chipped in. I have settled on informing the user as the solution. Rows below the insert or delete do not reflect the change until the cursor passes over them.
I did realize one big improvement - I had been using: delete row from table where idfield = .vbl changing to DELROW smoothed that up a lot. Next time you go to a fish restaurant and have Snow Crab, think of our observers on vessels in the middle of the Bering sea in February, along the ice edge, measuring a sample of crab. Then, a key-punch operator going over the data, and this routine helping the data correction routine to find one extra crab keyed in 120 measured from one trap. Thanks, Jim Blackburn Kodiak Ben Petersen wrote: > > Jim, > > (If you're RBW) I have tried a number of different things to get a > region to display properly after eeps have modified it's contents. > Inserting a pre-determined number of rows and only using "edi > using" works best. > > You can have your eep do > prevtab > recalc table > nexttab > > But the cursor lands on the first row of the region and most often is > not visible. I also had problems crashing RBase this way, though I > suspect that was more to do with with eeps conflicting with one > another. > > Ben Petersen ================================================ 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/
