Thanks, Nadya,

And sorry for misspelling your name.

>Yuri,
>
>Ok, you can not get my name spelled right :) I'll answer on your last question only, ok? Click Auto Quote at the bottom link of any message (before hitting reply).
>
>>Nadja,
>>
>>With DynamicCurrentControl I was not able to solve the "cursor stopped" problem. Anyway, it was a special project when they wanted to see and modify the report layout on the grid (with grouping headers, summary, etc.), and they are quite happy now.
>>By the way, when you replay here, how did you set the option to see '>' in the beginning of all previous lines?
>>
>>>Yuri,
>>
>>>I had the similar problem as Sandy and I asked the same question here just few >months ago. The answer was - use DynamicCurrentControl, and I think, that's >the ticket here and would be easy to implement. In my case, my manager just >told me disregard the whole idea and I did it differently...
>>
>>>Sandy,
>>>
>>>I did not need to do it with button in the grid, but with textbox. What I did was I set Column.DynamicForeColor and Column.DynamicBackColor to the very same color conditionally and set column.sparse=.f. and included return .f. in the textbox.When method.
>>>
>>>But even the textbox became invisible, still cursor went into and stopped there when user navigated through the screen and hit arrow/enter. So I had to force cursor go out of the cell. To do it, I added to the When method something like this:
>>>if (condition to force skipping)
>>> do case
>>> case lastkey()=5
>>> keyboard "{uparrow}"
>>> case lastkey()=24
>>> keyboard "{dnarrow}"
>>> otherwise &&eof(), bof(), others go here
>>> endcase
>>>endif
>>>
>>>Hope this help
>>>
>>>>I thought of using the When clause, but the button would still look like the >user could press it. My users would probably call me to tell me the button >doesn't work. Is there a way to actually disable it (so it looks disabled?)
>>>
>>>>Sandi.