Worksheet is protected--stopping the update.
Maybe disabling events would be required.
File in use

I think I'd try to think of all the things that could go wrong and keep a log of
which files got updated and which didn't in that log--include the first error
found for each file.





Nick Hebb wrote:

I have a routine that traverses a network directory, opens any Excel
file, checks for some data, updates and saves the file if necessary,
then closes the file.

I'm trying to brainstorm a bunch of test cases, so I can handle each
error/ problem gracefully. So far I've come up with:

- network connection failed
- read permission denied
- change permission denied
- file is password protected
- file contains macros
- prompted to update linked data

I wrote something similar about 5 years ago, and I seem to recall that
my list was much longer. Can anyone think of other opening, saving,
closing problems that might occur?

Thanks in advance.

Nick Hebb
BreezeTree Software
http://www.breezetree.com

--

Dave Peterson