Greg - correction: you got it in one: I had the designer properties set with the "AllCells" On, and had changed things in code.
My test app's prior behaviour was a 2 minute time to present (not 60s). Changing at the designer level gives me instantaneous" display. Now I can go back to attempting some prettiness and utility in the DGV. I had better take a look at my other test project (the OleDB virtual mode one), since I used the same form with DGV before coding the data paging. One never knows - maybe some weirdness comes into play (but I fear it's not going to be so simple). _____ Ian Thomas Victoria Park, Western Australia _____ From: [email protected] [mailto:[email protected]] On Behalf Of Ian Thomas Sent: Monday, May 02, 2011 11:05 PM To: 'ozDotNet' Subject: RE: DataGridView OleDB connection to Access MDB - virtual mode Hi Greg I just tried changing all those again, and it doesn't seem to improve (in fact, I often get ContextSwitchDeadlock errors when debugging, and 55 to 65 seconds to display after I click Continue). From what you write, the DGV is a pig of a control anyway? My 'other' error - the OleDB one - is very puzzling. It seems that with OleDB - Access, an index is wrongly calculated for the caching page fetch (but not for SQLServer). _____ Ian Thomas Victoria Park, Western Australia _____ From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Monday, May 02, 2011 10:19 PM To: 'ozDotNet' Subject: RE: DataGridView OleDB connection to Access MDB - virtual mode Hi Ian, just fumbling here, but I've had shocking performance problems loading DataGridView when any of the columns have "size all cells to contents" (I forget the exact name) and there are many thousands of rows. You can feel the poor thing groan as it loads all the rows and then freezes as it calculates the best widths. If I make a fixed width guess on all column widths then it can be magnitudes faster. Probably not your problem, but it's easy to forget -- Greg
