Prouduct ambiguity puzzle

terrypin wrote on 1/15/2017, 6:43 AM

Anyone know what's going on here please?
This screenshot was taken just after I had updated to the latest version of MEP 2017, 16.0.2.56 (UPD3) and used it to reply to a forum question. The taskbar showed that 2017 was active, yet the title says 2016.

I've yet to investigate this properly, but I think I was under the impression that I was responding to an automatic update of 2016, yet it was 2017 that got updated. And this means that it was the Program Data for MEP 2017 that was over-written, not for MEP 2016 as I thought.

Presumably this ambiguity stems from the new product announcment 'system', which I'd not encountered before?

Comments

johnebaker wrote on 1/15/2017, 10:01 AM

Hi Terry

What version number does your MEP 2017 show?

Mine is OK as shown below, and is at version 16.0.2.56

I also updated MEP 2016 from v 15.0.0.102 to 15.0.0.107 and there is no change there - still displays correctly as shown below

John EB

terrypin wrote on 1/15/2017, 11:23 AM

Hi Terry

What version number does your MEP 2017 show?

Mine is OK as shown below, and is at version 16.0.2.56

John EB

Hi John,

Same as yours - first line of my post 🙂

Could that apparently impossible screenshot arise after what I recall as the steps shortly preceeding it:

1. Opened MEP 2016

2. Got a message that I thought asked if I wanted to update it (but which might have asked if I wanted to update MEP 2017).

3. After following all the update steps including online re-actvating, prepared my reply re black titles and took the screenshot.

Terry, East Grinstead, UK

johnebaker wrote on 1/15/2017, 1:47 PM

Hi Terry

. . . . Got a message that I thought asked if I wanted to update it (but which might have asked if I wanted to update MEP 2017) . . . .

The only time I could think this would happen is:

If you were running both programs at the same time eg screen capturing one version from the other
One version was not fully shut down and was still running in the background with no visible interface - this I have seen happen when MEP crashed.

Then theoretically it may be possible that cross version update has occurred.

HTH

John EB