Hi Neil,

>What are the architectural differences you are talking about? If you want an extremely bad example of a grid then you should look at Navision!

In Navision it is extremely slow, no doubt. I think it was based on the Flexgrid. But of course all is handled within the framework. I've not seen Navision for about two years now (however my wife works with it on a daily basis) but since the average CPU power is getting better by the year, it is not so much an issue. The grid was only loading for the visible portion of the initializing the grid was not too bad (The loading of the grid started when the form already was visible).

For the rest, it seemed to do its job.

The datagrid in .NET seems not too bad either. It seems to be optimized for its task though there are some reports about slowness and as kevin reports it really does not matter how many records are in the dataset. However a post from the VB.NET TEAM: http://groups.google.nl/groups?hl=nl&lr=&ie=UTF-8&threadm=eIKJzEIdCHA.2060%40tkmsftngp09&rnum=3&prev=/groups%3Fhl%3Dnl%26lr%3D%26ie%3DUTF-8%26q%3Ddatagrid%2Bperformance%26btnG%3DZoeken indicate problems with large resultsets.

It may have to with a report that the upon binding the whole dataset is validated and thus every record has to be read. When using paging (a feature that does not exist in VFP), by default every record is read again. Maybe someone can confirm these issues were resolved in .NET 1.1 ?

Walter,