A (not better, not worse, just different) approach would be to add an event
handler to trap the slide change event.

On each slide change it adds the index (a long) of the current slide to an
array and updates a variable to point to the current index of the array.

The Back button calls a macro that goes to the slide pointed to by
array(current_position - 1)



In article 6, David M.
Marcovitz wrote:
First, you would need to make all navigation happen through links. Then,
each button that goes to the next slide or another slide will have to use
VBA, e.g.:

ActivePresentation.SlideShowWindow.View.Next

or

ActivePresentation.SlideShowWindow.View.GotoSlide 7

Then the procedures that contain those lines would also have to track
every slide that is gone to. I picture two variables: an array of
integers that has the slide number of each slide in it; and a counter to
count where you are in the array. Each click of a navigation button
would put the next slide's number in the array location in the number
held by the counter. A back button would simply subtract one from the
counter and go to that number instead.

Now that I describe it, it doesn't seem like it would be that hard to do.

--David


-----------------------------------------
Steve Rindsberg, PPT MVP
PPT FAQ: www.pptfaq.com
PPTools: www.pptools.com
================================================