>I'm creating a data-driven help system much like the one used in Foxpro (yes, there are reasons I'm not using HTML or the actual Foxpro help itself). I am populating an array used to determine the order of topics visited. The array is one-dimensional containing a HelpContextID number. I also store the last row number in a form property in order to determine where I am in the array; movement is Back (-1) or Forward (+1) in relation to that row number and I'm trapping for when I'm on the first and last row. My question is regarding what logic I should use to get the best naviagational result. Below are three examples of the array, each using different logic:
>
>A. Every topic visited is added to the array
>
>1
>5
>1
>2
>4
>1
>
>B. Only topics not already visited are added to the array
>
>1
>5
>2
>4
>
>C. Every topic is added to the array, but the previous matching one is removed
>
>1 (removed)
>5
>1 (removed)
>2
>4
>1
>
>...resulting in
>
>5
>2
>4
>1
>
>The last one (C) seems to be the best to me as it only takes into consideration the most recent navigation, but I wanted to know what others thought and if there was another scenerio that I haven't thought of yet. Thanks!
>
>Regards, Renoir

Renoir,
Removing visited might lead to inconsistent behaviour. Users especialy when browsing the net are accustomed to get 'previous' and 'next' visited pages and call new ones explicitly.
Cetin