backtracking

[Mark Bundgus <Mark_L_Bundgus@aud.alcatel.com>]

I realize this is an old issue, but I haven't yet seen a good example of
a working solution:

When using a display group to create a list of hyperlinks that a user
will use to drill down to the next level of detail:

i.e.  page main provides a list of note titles sorted by date 
      page notereader displays the full text of the selected note

The useful functionality of this application is that on the first page:
main, the user can search for articles by keyword.  This is accomplished
by matching their key word from a text field to a displaygroup
querymatch and performing a fetch on submit.


The end user has one of two problems:

If the user backtracks using the "back" button on the browser and
selects from a previously generated list, WO returns another page main
or the wrong note in page notereader.

If I follow the WO documentation and force backtrack refresh in
Application

self.setPageRefreshOnBacktrackEnabled(YES);

end users will get the generic Netscape navigator warning:

***
Data Missing

This document resulted from a POST operation and has expired from the
cache. If you wish you can repost the form data to recreate the document
by pressing the
reload button. 
***

If the user follows the instructions the correct data is displayed, but
we all know how difficult it is for users to follow
instructions....besides, this is not the elegant solution I am looking
for.

How has this problem been approached?

I have run the movie demo and found that it has the same problem with
displaying the wrong information or returning another list in page main.

Thanks,

Mark