Sam,
We tried this out, and we saw the same behavior you are seeing. According to Sam Bent, one of our databinding experts, one option would be to actually update the SQL database before navigating. If this is not the right behavior for your application, you could:

• Use KeepAlive=true (which I believe you have already experimented with. This should work, but of course will keep the whole page alive in memory)
• Keep a reference to the ListBox data source and repopulate it yourself
• Maintain static state for the page that the new instance of the page would reference and manipulate (assuming you are journaling by URI and not using KeepAlive=true)

(Thanks to Dave Relyea for help with the suggestions above).

Hope this helps,
Lauren

I sent you an answer by mail a few days ago, did you get that mail?

Somehow I got the feeling the mail got lost :(

First, thanks for the explanation, this is really helpful for me since I’m new to this browser-like stuff.

I had stumbled upon KeepAlive=”True” to get my pages to work, but to understand the ‘why’ and ‘how’ of this is very nice.

For my question about the Listbox, I had a Page containing a Listbox and a few buttons/Textboxes to enter stuff into the Listbox.

On navigating to another page and back to the Listbox page the content of the Listbox was gone.
Should a Listbox get persisted just like a Textbox, and I was using it wrong?
(do you need some source to clarify? I could squeeze an example in a comment, I guess.)

oh, and thanks a lot!