>>>>>...Carlos buffering doesn't reduce performance considerably. I couldn't follow the whole thread but did you use "activerow" anywhere in this grid (ie: as a RO controlsource)? It's the most performance penalty I could find for grids. When I first used it and table grow to some large amount users would nearly go for a coffe break after pressing up-down arrows.
>>>>>>Cetin
>>>>>
>>>>>Cetin,
>>>>>We've talk yet about it: In the past i have used the activerow property, but i've removed them from the code. No results. The table is very long, but i'm using it as a chind record of other one. Doesn't matter how long is, when you begin your session adding items, performance is good, but each record you adds, go decreasing, and after 80 or 90 items added you can have a long 'dinner break'.
>>>>>
>>>>>You close the form, re-enter and performance returns good. I've tried all the sugestions in this thread but no results. Now i don't know what more do.
>>>>>Carlos.
>>>>
>>>>Sorry, I missed the start of this thread. What is grid.recordsource? Do you use some kind of buffering or temp relationships?
>>>
>>>recordsource of the grid is a table alias which is a child of other one. I have pessimistic table buffering in the child table.
>>>The grid has 18 columns, 2 with sparse checkbox, one with no-sparse commandbutton.
>>>I only let the user modify one record a time and he must validate it to edit other one, but rowbuffering is not good for me for other questions.
>>>I have not count, or select commands in code that go bigger adding records.
>>
>>Does your grid show all table records? If yes, table buffering might be cumbersome. I would think here about parameterized view/cursor, i.e. when user moves pointer along parent table (e.g. using combo) new view/cursor repopulated.
>
>The grid only shows the records that match the parent table data and the relation within the two tables. The parent table is a temporal one with only one record, making changes in the parent tables from controls in the form, i refresh the grid. I've never used views in VFP. ¿Are they 'autoupdatables'? when i make a change in a view, does the original tables asume changes? ¿Can this be a solution to performance?
>Thanks

Yes, it will be solution. Having few records in view or even in plain cursor you will 'lighten' grid tremendously and will get control how and when data should be updated. In a case of view it's the same TableUpdate(), in a case of plain cursor it's SEEK and INSERT/REPLACE.