The question:
When running the workbook 'inbound' function, if there's a failure in the "book = HSSF_open(file_name)" loop because a given workbook in the group doesn't exist in the path, then no 'open' works after that even though subsequent workbook(s) in the group do exist. The monitor group around the 'open' just prevents the halt, subsequent existing book(s) still fail on the open. I've tried "HSSF_end_object_group()" (in the on-error) but that fails as well. (I know the program logic is good because if I'm specific about the single workbook I want to read, it retrieves it just fine. What should I be doing after an 'open' legitimately fails? Or do I have to do an existence test in the host server before I attempt the HSSF 'open'?
The wish:
If there's a way to protect the sheet(s) of a workbook and the workbook itself (with a password) from within my creation program, I'll die a happy man.
When running the workbook 'inbound' function, if there's a failure in the "book = HSSF_open(file_name)" loop because a given workbook in the group doesn't exist in the path, then no 'open' works after that even though subsequent workbook(s) in the group do exist. The monitor group around the 'open' just prevents the halt, subsequent existing book(s) still fail on the open. I've tried "HSSF_end_object_group()" (in the on-error) but that fails as well. (I know the program logic is good because if I'm specific about the single workbook I want to read, it retrieves it just fine. What should I be doing after an 'open' legitimately fails? Or do I have to do an existence test in the host server before I attempt the HSSF 'open'?
The wish:
If there's a way to protect the sheet(s) of a workbook and the workbook itself (with a password) from within my creation program, I'll die a happy man.