|I have my Nikon View software set up to cerate a sequentially-numbered IMG folder in my photo directory. When I load a CF card into my reader, Nikon View launces automatically and offers to write the images to the hard drive. I ok this, and it creates a new directory in the host folder and copies all the images to this folder. The originals remain on the CF card at this point. The copied files are also "originals" in the sense that the EXIF data are unchanged.
When all the files have been copied, Nikon View launches a page of thumbnails. I can click on a thumbnail and view it in Nikon View at full size, a quick way to review my work and see what's waiting for me. As long as I close the image without DOING anything, the EXIF data remain unaltered. If I do anything (like rotate to vertical) when I try to close the image in NV it prompts me to save changes. If I refuse to save, the EXIF data remain unaltered.
When I work on challenge submissions (indeed, on any image) I open the original in PS and immediately save-as a .psd file to a different directory. If the original were, say, "DSC_1001", then the new file is named "Fisherman_wide_DSC_1001" and saved as a .psd file. This way, I can always go back and find the original by referencing the DSC# embedded in the image title on the working copy.
I've been validated several times, and thus I can presume that this workflow (opening with Nikon View and viewing both thumbnails and originals) in no way alters the EXIF data. I would presume the same is true of ACDSee; as long as you don't save any changes, the original EXIF data remains intact.
Is this presumption wrong? I am not clear from what I am reading here. Does ACDSee actually alter the EXIF data simply by the act of shepherding the upload and launching thumbnails?