I since found the answer myself: you would think that OfficeXP would
incorporate without conflict vba programs created under prior versions but it
does not in this case...I recreated the program in XP and save is now
permitted !

"André Boileau" wrote:

Why is it that the user of my Excel vba program can not save the Excel sheet
while the project is password locked ? Excel's message (not an error message)
tells him project must be unlocked before ? I can avoid the problem by
incerting the locked code in another Excel file and joinning them with
"Tools/References...." but there must be a better way ?
Thanks for your help.
--
Popsie