Hi Guys,
 
I'm flinging this out to everybody/every place i can think of.
 
I have a major problem, and some odd behavior, from the SPGridView and i'm 
hoping somebody here can give me a clue as to what to fix (or who to shoot if 
we can't fix it).
 
Scenario:
 
We have a page, which contains 4 web parts which each contain a SPGridView. I 
have enabled sorting and filtering on all grids and that's working - well 
that's what i thought anyways. If i sort, either by using the dropdown or by 
clicking on the header, on the first grid then it works. The grid sorts as it 
should. If i try to sort by using the dropdown (from the header in SPGridView) 
on either of the other three grids, it'll work the first time, but when the 
page reloads and i try again, i get a javascript error and the dropdown doesn't 
appear. At this stage, the first grid still works fine. Other odd behavior is 
that the sort has also been applied to the first grid on the page (the one that 
still works). This is particular to columns that exist in all four grids. If 
the first grid doesn't have a column identical to the other grids, and i sort 
by any of the other three grids, then it's not applied, yet the javascript 
error still comes up.
 
the header sorting (clicking the header on the column) is still working on all 
four grids, except for the fact that the sort that i'm applying to grid 2,3 or 
4 (and if the column exists in the 1st grid) will also apply itself to the 1st 
grid.
 
The data in all four grids are different and pulled down via an 
ObjectDataSource. 
 
Has anybody seen this behavior before and (hopefully) are you able to point me 
to a solution (except, don't use SPGridView)?
 
Regards
Brian H. Madsen
Microsoft MVP Visual Developer ASP.Net



------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

Reply via email to