>Hi!
>
>>>As far as the records jumping around on the grid: Is the value of the combox or another field on the grid contained on an index used to sort the table that is the grids data source?
>>
>>Yes, and this is my biggest problem. If the user changes any of the fields, which is part of the index expression, the record jumps to another location. Next/Prev buttons also would place to another location. I want to keep user at the same location, as he/she was.
>>
>

>BTW, Record will not jump until you Refresh grid or set focus to it. Just try a simple sample with default grid class. If this is for 1 record editing only, do not ever call the refresh. Well, if you have row highlighting, this is somewhat tricky. Let me know if you need the description of way of how to organize Dynamic* depended on RecNo() without calling of grid.Refresh in the AfterRowColChange.

Yes, I found it too. I commented out call to dodefault(nColIndex), which called Highlighted grid code and our wgGrid code (the last one I don't want execute at all). It seems to work fine without Grid.Refresh() (I still need it if I update status field to show it in a proper color). It seems to resolve my problems with "loosing the current grid highlighting" and some other anomalies.

>Of course, when user change focus...
>
>P.S.: I hate to use grids for data editing too.

In most of my applications I don't use Grids for editing, only for displaying info. This one was started by my colleague in 1999, and was turned to me less than month ago. I practically re-designed it from scratch and I'm still working on all new user's requests.

I'm going to start a new thread for some interesting user's request, which should apply for several applications, not only this one.