i guess no one has had this problem. i found out what is causing it.

 double post back is coming from  the pagebase.ascx.vb  it has to do with injecting client script.

the paging control doesn't update the urls unless you turn it off ctrlpagingcontrol.visible=false and then turn it back on. there isn't a refresh method or redraw. it's render method is looking for a htlmwriter object that doesn't exist in the sorting code. so it is easier to turn it off. update control. then turn it back on. it updates all of the links correctly and it isn't noticable on the user side. wierd.

the navigateurl function mangles the query parameters (even if encrypted). it looks like a regex issue. i just don't have time to track it down.

i solved all of the sorting and paging with cookies.  query is applied and bidrectional sorting is applied on the query and cleared to the defaults on clearing the query. i really hate doing that but, it works for now. i posted this in the talk about it originally because i didn't think it was in the UDT mod. someone moved it here so i tracked down what was happening myself. these are core issues that can be addressed or at least documented so we can work around them.

richard

when you use ctlpagingcontrol.QuerystringParams and send a your query string. is gets mangled after 4 or 5 postbacks. for some reason it injects a square for this '% in the string. it has something to do with navigateurl. your string is sent there as a 2 element array with some info the paging control needs.

i had to resort to storing the encrypted string in a cookie to get it to work consistently. i didn't want to put an unencrypted query string in a ccokie.

richard