For the type of work I do, I must lock down Excel spreadsheets for legal and risk reasons. We try to automate the spreadsheets as much as possible, and the main focus on current work is save and send functionality.
I have that working perfectly - including the generation of filename/subjectline through either specified information in a setInfo procedure or derived from information input by users.
However, when the user launches a save and send routine, if they cancel the save procedure (which is required for the send routine) it produces the FALSE.xls file.
Has anyone figured out how to prevent this?
Bookmarks