MichelBParis Thanks for all of your suggestions and input in this forum. For what it's worth, I can tell from your comments on the use of PSE that I do not have your depth & breadth of knowledge regarding PSE. I have found your suggestions on the use pf Photoshop very useful. As some background, I have 30+ years of extensive experience (with companies smaller & larger than Adobe) designing, developing and supporting most aspects of software & hardware development, I have a pretty good idea of what happened here. IMHO these are my thoughts: * ALL software has bugs. Therefore when ANY product is distributed, it needs to have a method to update it. Adobe of course, knows how to send out updates. If you doubt that, just think of Adobe Flash Player. It seems like they are updating bug fixes every other day. *It is easy for PSE to be updated. Please notice the built-in "updates" tab. *Although I cannot say for sure, it is customary for corporations to coordinate changes to their software with major partners. By this, I mean specifically, Google probably knew that they were planning on changing the interface with maps and distributed the specs to partner companies way ahead of the changes. The fact that PSE V15 works fine, probably proves this. * To facilitate updates and bug fixes, most competently written/designed software is written in a modular format (there are several fancy acronyms for this that overpaid consultants like to use 🙂 * This means that most or all of the mapping portions of the code in PSE15 is likely identical or 90% the same. I have NOT looked at PSE15 ( I have PSE13). If the mapping screens of PSE15 look the same as previous versions, the code probably is the same. If they changed it in later versions, they still could just change older versions to use the new blocks of code. It should be rather easy, unless they really screwed up the design architecture. *Back to PSE15. Adobe released it a year before Google changed their interface. Since PSE15 was NOT broken by the Google release, it rather strongly implies that Adobe has known for a long time about the changes. At least long enough to re-code their interface with Google Maps. Or perhaps they pushed an update to PSE15 prior to August. In any regard, I would bet, that there is no significant reason they cannot easily fix prior versions. Adobe is know within the industry for being quite arrogant. I hate to say it, but I doubt they really care that they are pissing off PSE customers. The only hope for customers, is some sort of class action suit, since they probably have violated several countries (or USA States) consumer laws, but I am not going to hold my breath. In case anyone from Adobe is reading this (doubtful). Here is my summary: I am certain you can easily fix the issue. Regardless of what you think, it is not good business to piss off customers, even if it is a small part of your product base, it will impact you. Large customers also notice this behavior.
... View more