Lily and TLC, Thank you both, this is my result. if ( window.cpAPIInterface ) { window.cpAPIInterface.setVariableValue('myURL', document.location.href.substring(document.location.href.lastIndexOf('/')+1)) } window.localStorage.setItem("myCallingMenu",window.cpAPIInterface.getVariableValue('myURL')); The code looks for the current URL in the browser and then strips out just the filename. The filename is then placed in a variable named myURL The contents of myURL are then stored on the hard disk in the browser local storage in a variable named myCallingMenu. Why do I need this? I will use this in a menu system. I have a number of seperate menus (menuDoctor, menuNurse, menuAdmin, menuPharmacy etc etc) Each of these menus calls projects specific to those job roles. However, each menu can also call a common project, such as 'infection_prevention'. When the infection_prevention project finishes I need it to go back to the menu it was called from, (doctor, nurse etc) So I will use the code above to store the filename of the calling menu in the myCallingMenu variable on the disk, and then when infection_prevention finishes it will read the filename in myCallingMenu and return to the correct menu. (I've got the reading code working as well) Why do I do it this way? I don't want to use the Aggrigator thing, I find it too cumbersome. If I tried to combine all the projects into one file the size would be just too large. Our network is slow, so small projects work well. Using individual projects allows me to ammend one section without having to recomplie the entire project. The PC I run captivate on to create the projects is a bog standard business PC designed for nothing more taxing than word processing, so Captivate is slow, therefore small projects are better. Large projects crash more than small projects. (I do all my work on my local drive, working across a network crashes even more) I hope this will be of help to anyone else who needs a similar thing. Peter Cardiff (Still overcast and grim) Wales UK
... View more