Hi Mitch,

Mitchster2 said:

Upon looking a little closer now, am I to understand that it is only recommended for 'read only' grid presentation?

No, that is not correct. Where did you get that impression? I think maybe the milltion rows sample is read-only, but there are other samples that demonstrate how to allow updating, deleting, and adding. You just have to handle a few more events for those cases.

I think you have to look under the DataSource samples, not the WinGrid samples.

...\WinForms\2012.2\Samples.EN\DataSource\CS\Virtual Mode Sample - Extended

Well, I was looking at the Samples and saw the 'one million records' example using the UltraDataSource. Although we generally do not load that much data, in one of the applications I have written with Infragistics controls, a manager may want to have that much 'breadth' to analyze against or quickly filter through. I am able to get up to around 700,000 using datatables and standard binding and 'imagined' the WinDataSource as an athletic, low body fat version of the MS options. Upon looking a little closer now, am I to understand that it is only recommended for 'read only' grid presentation? Is the trick to its lower memory consumption just the pre-allocation of Record Count? My application allows editing but not record Adding or Deleting, couldn't it work for such an 'editable' grid?

Thanks,

Mitch

I am using a variant of this  - I couldn't quite get the grid to look how I wanted it to, based on the original data source, so I create a temp UltraDataSource with the layout I want, and fill it during initialization. Yes, it's tedious, but fortunately in my case anyway the size of the data is fairly small.

My question is - after a bunch of manipulation to the temp datasource, and I need to store all the data back to the original - is there a simple/single "dirty" flag in the UltraDataSource that I can check to see if all that work is really necessary?

(Apologies to the OP for potentially derailing the thread...)

Rob