>>>>>>Does anyone know how to ensure that the current record in the grid allways has the record mark on it? In my opinion this has never worked the way it should intuatively work. Am I wrong?
>>>>>
>>>>>I agree it doesn't work right. I work around it by setting focus
>>>>>to the grid momentarily every time I move the record pointer
>>>>>programatically. You can eliminate the screen "blip" of the setfocus
>>>>>by doing a THISFORM.lockscreen=.t. before the setfocus, and a
>>>>>THISFORM.lockscreen=.f. afterwards.
>>>>
>>>>I've also done this but I am having trouble with a custom grid class contained within a container class. I need the container to fix another problem. I needed a true lostfocus event and the grid was repainting itself after the last grid event had fired. I was just wondering if someone else had a different solution before I dig in and add this to my class. After three versions of Windows based foxpro versions I would think this would have been fixed.
>>>
>>>The best remedy here is to color current record in grid and don't use RecordMark.
>>
>>Ive been working on that but it seems to be very slow. Do you have any advice as to what to do and what not to do?
>
>You use DynamicBackColor property, and this is not slow.

When you use the up and down arrow keys to navagate through records, the colored row lags noticebly behind. My question refers to: Does it matter what color, if the columnsources are calculated will that slow navagation further, use lockscreen or not ... etc. Thanks