Barbara,

The problem was exactly that; a combination of the the Refresh and highlighting logic that was built into the class. Thanks for the advice (Will and Cetin also). The client wants the highlighting, but not the delay. Any suggestions on how to have both?

Renoir


>Renoir,
>Will's suggestion that you remove the Page2.Refresh() code would have been my first suggestion. If the delay is still too long, then you might comment out all of the "Page2 Active", "Grid Highlight" and "Seek Logic" code to see if there is another reason the code takes so long to run.
>
>Barbara
>
>
>>I've taken over a project and there are some efficiency issues that I would like some advice on. To simplify, let's say that I have 2 pages in a frame where the 1st contains a grid of a master table and the 2nd has some detail based on a child table. The current functional logic is that whenever the pointer moves in the master table (ie, grid on 1st page) it checks to see if there is a match in the child table (detail on 2nd page). If there is a match then the 2nd page becomes active, but if not then the 1st page remains active. They have seek logic and a form refresh in the AfterRowColChange method to determine the value of a logical form property. This property is then used to determine the active page. It works, but the problem is a significant delay when moving in the grid on the 1st page. I tried using eof() based on the relationship that exists, but I didn't see any change in performance. I should add that the parent class also has logic to handle highlighting the row on the
>>grid. Any ideas?
>>
>>Regards, Renoir