kdlc wrote:
I've seen this kind of behavior before in Vista. It happens if the PDF file you're trying to save is in use by another process like adobe or the Vista Preview Pane.
kinda scary if your users are working in a really important PDF file and it gets wiped out when saving changes ...
With every Windows version, Adobe Reader locks the file it is showing.
It won't get wiped because it's locked.
It's up to your application to retry Save() if it failed because of a lock.
Like Office does: if Save fails, it automatically displays the SaveAs dialog.
Or have your application lock the PDF file. This prevents Adobe Reader to lock it and saving changes will succeed.
This can only happen if you don't lock the file allowing your users to lock the file by opening it with Reader while your application has it in memory and allows modifications.
Not scary if SaveAs jumps in if Save failed.
No need to be scared if you let your users work with carefully tested applications ...