I can't believe Adobe implemented something like this, it makes absolutely no sense to me, and since they did implement it, they absolutely positively need to create a way to disable it.
Example steps to reproduce:
I scanned a collection of documents and named it "scans.pdf" I did my work with them and deleted the file off of the desktop and emptied the trash.
Later, I then scanned a different group of documents, named it the same "scans.pdf" and when I open that file in Adobe Acrobat Pro DC 2020.009.20074 guess what happened? You got it, it loaded the old file which I had already moved to the trash and emptied.
If I open the document in Preview, of course it is the correct document, but Adobe keeps opening a cached version of it.
Simple workaround:
I renamed the file (to "get-a-clue-adobe.pdf") and since the name changed, it now opens the correct document.
Dan Dawson
supported this idea
·
I can't believe Adobe implemented something like this, it makes absolutely no sense to me, and since they did implement it, they absolutely positively need to create a way to disable it.
Example steps to reproduce:
I scanned a collection of documents and named it "scans.pdf" I did my work with them and deleted the file off of the desktop and emptied the trash.
Later, I then scanned a different group of documents, named it the same "scans.pdf" and when I open that file in Adobe Acrobat Pro DC 2020.009.20074 guess what happened? You got it, it loaded the old file which I had already moved to the trash and emptied.
If I open the document in Preview, of course it is the correct document, but Adobe keeps opening a cached version of it.
Simple workaround:
I renamed the file (to "get-a-clue-adobe.pdf") and since the name changed, it now opens the correct document.