<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Thanks Pat and others for suggestions re the ‘insufficient editing priviliges’. We’ll categorize that error as related to sunspot activity and hope it disappears in XOT2.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To try to answer your question John the menu (graphic below) is html/js and inserted via a flash page. It reads the parts/module names from a database array, then turns on / off part and module marks as the user progresses, and updates the database. I’m afraid I don’t really understand your events and how we might be able to use them. Right now a connector page brings you back from a ‘module’ (just a sequence of pages) to the main menu, but we’re looking for a more elegant way to navigate.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=197 height=160 id="Picture_x0020_1" src="cid:image001.jpg@01CEF756.D91EDE10"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If we use PageID to code the ‘start of module’ pages then the menu will know (if Part 2 Module 3 is clicked, for example) to go to PageID=P2M3P1 (part 2 module 3 page 1), and so on. So I think we can navigate to the first page of each ‘module’ by coding the PageID as long as it doesn’t change. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The more awkward issue at this point is coming back from the last page in a module (how do we tag it as such??) to the menu. Right now we can use an extra ‘embed content’ page as the end of page of each module to send it back to the menu, but that means another empty page just with script at the end of each module. Is it possible with your events to add specific script coding to each page? Could we tag a page as ‘EOM’ (end of module) and on the unload event navigate back to the menu? Sorry but I’m not understanding how we might be able to use the page events, or your suggestion below:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><i><span lang=EN-US style='color:#1F497D'>The plan would be that the menu page would load, hook into these events and as they fire, we get the pageID and tick that off from a list. This could be automatically generated too when an XMLLoaded event fires or something…<o:p></o:p></span></i></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks <o:p></o:p></p><p class=MsoNormal>RonM2<o:p></o:p></p></div></body></html>