Re: Datagrid aggregation in each cell

Ryan, and Cor, Thank you for your responses.

Here's some more information. The number of cities is 40 at this time
and is likely to grow. I simplified my requirement for explaining it.
Actually, the Errors and Failures are divided further into groups -
like for instance Error Group 1, Error Group 2, Error Group 3 Failure
Group 1, Failure Group 2, etc. which means, more columns - about 20 or
so. There's an aggregate column at the end as well.

The input for this search page are a date range, type of result -
whether in % or actual count. As the date range gets wider, the more
chances of runtime error in the present implementation.

Here's how the tables look like (I simplified it once again for the
sake of clarity)

tblCitiesEvents
CityEventID int PK
CityEventDate Date
CityID - FK
fName
lName

tblCities
cityID - PK
cityCode

tblEvents
eventID - PK
eventDescription

The existing stored proc is the size of about 4-5 printed pages. Yes,
the events table is indexed; this obviously has the most number of
records.

Given this many number of columns and rows, having Labels may not be
practical. But please correct me if I'm wrong.

Thanks for any/all inputs.

.