Ronnie,

All your problems lie in fact, that the grid re-construct itself (and Vlad already tried to explain it). First of all, you don't have to put assigning controlsources in the grid Refresh method. Do it once in the design time. As I understand, this grid would be always used with o1 alias (correct me, if I'm wrong, I didn't see it right now, so this is from what I've seen ysterday). In this case after you re-create your o1 you probably don't have to do anything (just refresh the grid), I'm not 100% sure about it, I have to test.

Basically, you select records into the same cursor name o1, which is RowSource for the grid. Right? Let's see, you may be don't need to do anything in this situation and the grid preserves its settings. But you should read Vlad's FAQ about grid reconstruction and I have to re-read it too.


>You can make changes..no problem.
>
>I now understand that the container object was not necessary. I assume
>I could just of added a class based on a grid and that would have
>been sufficient. (correct me if wrong)
>
>Basically the area of mystery to me is the following:
>
>What concept affects the text1 control in the grid so that it does not
>respond as when it is accessed as an external object vs. when the object
>is placed directly on the form at design time.
>As you can see from the form I add a selection criteria object (which also does
>not need to be a container) and the grid object and then have user
>just selecting certain records from the table and modifying them from
>another form. The functionality that is not working is when I select records
>into the cursor and re-populate grid, it does not get the focus and I cannot
>click on the grid and get it to do anything..I put a =messagebox() in
>one of the text1 controls just to test and it does not work either.
>
>Ronnie