Yes I did Gord, thank you. I did get food for thought from one of the posts on google involving change events....I'm going to try this out on Monday.

Thanks again.

Nope, my theory of two posts ago did not work. I'm at the end of my rope. Just can't understand why the spreadsheet works flawlessly on local drive and only sometimes on network.

Oh well, time to dump excel for this project...just too unreliable.

After a long time of pulling my hair out over this 'document not saved' problem, I may be on to something and wanted to bounce it off the experts.

I noticed that sometimes when I get this error, my 'Module1' macros were not showing (or deleted) in the VBA editor. I moved all procedures from Module1 to the 'Thisworkbook' module and then deleted Module1. Maybe virus program deleting Module1.

Since I've done this, I haven't been able to replicate the error.

Does this sound plausible?

Well, after much heartache, it appears we found the source of the problem. My excel file with vba code in it often gave a 'Document not saved' error when run/saved on a network drive. It didn't produce this error on a local drive.

The network drive in question was part of a RAID disk system (apparently this stands for Redundant Array of Inexpensive Disks). I am told that this disk system is not the on the actual server, but is run through the server.

Long story short, when the excel files in question were moved directly to the server's hard drive, the problem as gone. There is obviously some kind of conflict with excel/vba and the RAID disk setup.

While this is not a resolution (since we still don't know why we can use the RAID disks), we've moved the files to a direct location on the server and are now able to run the excel files normally.

Hope that helps someone out there. If anyone has discovered a solution for the RAID system, I'd love to know.

Thanks