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

Reply via email to