Limits of the datagrid

  • Thread starter Thread starter Altman
  • Start date Start date
A

Altman

I am planning on creating a datagrid in vb.net. The purpose of this is
to show the distance between one location and another. My plan is to
have a location table, and then have a location_distance table. The
location_distance table will have the source location and the
destination location. I intend to show this in a grid where the
columns are locations and each row is a location. My problem is, I am
thinking that the location table could get as high as 200-300 records.
This means the grid will have for instance 300 columns and 300 rows. I
have looked online to see what the limits of the datagrid are but I
cannot find them. Also I am worried about performance. A 300 x 300
grid will mean 90000 cells. Will this take to long to load? Is there
a better way to do this that I am not thinking of. I will probably
provide a filter to the user to limit the number of columns/rows shown
to the user but the grid can still get rather large. Also what is the
best way to create this grid. Is my only option, to create each column
and each row manually?
 
Altman,

I think that your main Limit is that you cannot fix the Vertical (Row)
header.

I do not know so a grid, which has that, but I think that that is the first
thing you have to Search for. I write this maybe knows it, making the
underlaying Generic list is probably not the problem..

London Paris Amsterdam
London
Paris
Amsterdam

Cor
 
A 300 x 300
grid will mean 90000 cells. Will this take to long to load? Is there
a better way to do this that I am not thinking of. I will probably
provide a filter to the user to limit the number of columns/rows shown
to the user but the grid can still get rather large. Also what is the
best way to create this grid. Is my only option, to create each column
and each row manually?
Click to expand...


Firstly... who needs a 300x300 table? How readable is this going to be?

You might want to think of using some filters, search screens, etc?

Or why not use 2 combo boxes - Origin --> Destination = Output.

Much simplier and easier to read (especially for lots of locations).
 
Back
Top