Greg I do need to do a couple of other DGVs (quite different), so I'll use the designer for those - the tasks / applications have fixed 'schema', so it's appropriate.
I had a devil of a problem with Virtual Mode DGV and the Jet or ADO Provider for Access (from memory), a year or so ago. There is a nice example from Microsoft for using Virtual Mode, and for SQL Server it seems fine but not for Access (and of course I had daily MDB files provided online, so read-only access to them would have been much nicer / quicker with virtual mode). _____ Ian Thomas Victoria Park, Western Australia _____ From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Sunday, January 08, 2012 1:13 PM To: 'ozDotNet' Subject: RE: DataGridView (WinForms) - .RemoveAt Hi Ian, I remember years ago having similar problems with the DataGridView. I then adopted the practise of binding my grid to a strongly typed DataSet I make in the designer. Even for knock-up utilities I find it convenient and readable to make an XSD and bind the grid to it. It's then easy to go myrow.Delete() and AcceptChanges() and the grid responds. I'm not sure how you're filling your grid rows, so maybe my comments are not directly relevant but I thought I'd mention it anyway. You're brave to get into DataGridView virtual mode, as even though I've happily pushed the grid to its limits over the years I've never needed virtual mode before. Strangely enough, several years ago I wrote a nearly identical app to yours. It scans folders for files with identical MD5 hashes and shows the duplicates in a tree and you can then "clean" the duplicates. I just ran it and to my surprise it still works, but it's a bit quirky and not suitable for public consumption. Cheers, Greg
