Took me some time to get to boiling about this issue. Say you work with multiple files, each in their folders by type of activity (forecasts, client data, stocks, offers etc nothing fancy, regular firm doing its job). Repeatedly but not as a rule, the file opened in directory X and needing saving as the newest iteration of that file (backup purposes) cannot be depended on to be saved in the same directory X because the program suggests another saving address and if in hurry, file gets mis-saved.
so, in this scenario Open… Work()…Save As… the saving address filled implicitly needs to be the address the file resides in !
Simple Save…seems to work (saving implicitly in the directory the file resides in) but can’t be 100% sure.
Very annoying saving behavior, that started some months ago.