UPDATE:

I checked out the v13wstat3 of the page using Fritz Onion's v13wstat3 decoder for .net 1.1 and instead of decoding it gave me:

There was an error decoding the v13wstat3 string: Key cannot be null. Parameter name: key

Not sure if this is a bug in the decoder or a problem with my v13wstat3 but either way it doesn't help much.

I'm not dynamically creating any controls in the module and I checked the module definition to ensure it's cache duration is set to 0. It is. I also tried setting it to -1. Same results. It doesn't seem to matter whether I'm logged in or not either. Either way the v13wstat3 is only preserved on static controls like textboxes and drop-down lists - when I set a v13wstat3 key value manually it is lost.

I think I found the resolution. I believe all of this has something to do with how DNN caches data pulled from the database. I was passing a filter expression and sort expression that was dynamically concatenated into the WHERE clause of the select statement in the sproc. For some reason requerying with those parameters changed resulted in the same initial data being loaded into the datagrid.

Rather then digging into the issue further, I rewrote the DAL the way it should have been to begin with - the datasource of the datagrid is now a dataview based upon the arraylist that comes back from the DAL. I removed the filter and sort expression params from the sproc and now are using them as arguments of the dataview. This works fine and is obviously a better alternative than somehow trying to hack around with the caching - the data is always the same, it's how it is viewed in the datagrid that's important for this project.

Regards,

K