I think there has been some discussion of problems with saving files (share violation messages, etc) with version 7.
I am still on version 6, but have been having a problem working out some sensible way of ensuring that I have actually saved a file when I think I have. I first noticed the problem when I pressed File|Close after having worked on the file in question for some time. Usually when I do this NB tells me the file isn't saved, and asks me if I want to save it. This time it just closed the file, and when I checked I found my only copy was about 4 hours old. Luckily I was able to rescue the work by re-naming the autosave file, but I decided in future to do "Save as.." backups to my A: drive regularly.
This works OK (when I remember to do it), but it doesn't, of course, solve the problem not knowing if and when the regular File|Save is going to work. I noticed on one occasion that after doing a "Save as..." of a file I was working on to my A: drive, saving the identical open file to my C: drive didn't "take". Again, there was only an earlier version available. Yes, I had the A: drive's backup file, but I should also have had an up-to-date C:drive file, too.
Could it be that once a file has just been saved, whether to another drive or "autosaved", the program won't do another save until some more time has passed, or further work has been done on the file?
I know some people are saving manually every few sentences in order to protect their work, but that seems a rather painful workaround for this problem. I haven't yet worked out a systematic explanation of what is going on. Do people still have the problem with v7? Is there a simple routine I can follow to stop it happening?
Derek