Thanks Razzak. That sounds familiar but I did not see it in the notes I was looking at. Will do it.
James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Tuesday, February 10, 2015 1:25 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: scrolling region At 12:25 PM 2/10/2015, Albert Berry wrote: >Perhaps I am misreading your post but you do not use <> around the >table/view name. If the form is on the view, WorkProc ? will be the >table. >PROPERTY TABLE WorkProc 'REFRESH' Here's the most eloquent method of saving, refreshing, as well as maintaining all WHERE clause(s) of underlying table in a form, without screen flickering: PROPERTY TABLE formtablename 'CLOSE' PROPERTY TABLE formtablename 'OPEN' RETURN Very Best R:egards, Razzak >On 2/10/2015 8:57 AM, Jim Belisle wrote: >>We use a scrolling region on a form for our daily edits. >>We often add rows. >>I have the scrolling region based on a single table view that is presorted. >>If we leave that edited employee, go to another employee, then come >>back to the previous employee, the sort is perfect since it is based >>on the presorted view. >> >>If my user inserts the row lets saw at the bottom of the form (meaning >>out of sequence) I want to refresh the view so the new row will shift >>to the proper location. I tried the following in both on row exit and >>after saving row EEP. >>PROPERTY TABLE <Workproc> 'REFRESH' >>Neither worked. Is this the proper code for what I want to accomplish? >>Since above is the view name, should I use the table name that is the >>basis for the view instead?
