To me, such error handling IS a form of information.
There is nothing wrong with that approach.

If it is you creating these protected file, you could add a Custom Property
("HasPW") to the WB, which you can check beforehand with the MS DSOFile.dll.
But it hardly seems worth it.

NickHK

wrote in message
ups.com...
Thanks for the reply, that's the solution that I ended up implementing,
but it really would be nice if there was a way to simply test for it,
rather than using an error handler to determine that it didn't open. I
appreciate the response though!