In case you can't just change the library definition (=same libref but another path) but you actually need to change the name of the libref in your specific document: I haven't found a menu item in AMO which allows you to do this BUT you can do it using the migration wizard (worked for me). https://support.sas.com/documentation/cdl/en/bidaag/69541/HTML/default/viewer.htm#n0oy93cwp7oc51n14p509zbjjzdz.htm    On my laptop this wizard can be found under:  C:\Program Files (x86)\SASHome\x86\SASAddinforMicrosoftOffice\7.1\MigrationWizard.exe and changing the library was a simple point & click operation.   Another hack option which also worked for me with Excel 2013 (you want to try this on a copy of your Excel): You can open a .xlsx with an archiving tool like WinZip or 7-Zip and then modify the path directly in the XML. There is a risk that you corrupt the .xlsx - but it worked for my with my sample file and changing the libref from "sashelp" to "sasuser" ... View more

Hi thanks for the reply, I will read up some more on it, I was struggling with the fact it wanted to do every possible combination rather than just make sure it included specific variables unrelated to the others (not sure if that makes sense) ... View more

RW9 you proved I am wrong (release management Excel) as you described that, that is very nice way to take care for that at you site. Eguide is not having an easy way back to Excel (no DDE/VBA) you could build something yourself as EGuide custom tasks. When the sas server is run at Windows you do possible some things. ... View more