Sage 100

From a Product Advisory Call this week: We were all so surprised to learn a tip (kudos to John Nichols!) about the Crystal Conflicts folks have between a test mode of 2018 while still using their prior Sage 100 version. He told folks that in order to avoid the Crystal 2018 conflict, you can simply rename the pvxexe.config file in the 2016 or 2017 versions of Sage to something other than pvxexe.config, then copy the 2018 version of the pvxexe.config file into that older Sage 100 version's Home subdirectory, and all of your Crystal conflicts will disappear. (And he also tested it in 2015, by just adding the pvxexe.config to the Home directory, but didn't go back farther than 2015 in his testing process.) We tried it, and now we can access 2018 Crystal as well as the previous 3 versions of Crystal without having the Crystal conflict. I can't guarantee the results for everyone, but it sure worked for us!

Also, For Sage 100 Advanced (or premium) each workstation client has a MAS90\home folder so it needs to be copied to each client.

Just to verify - does this work **without** installing a full 2018 to every workstation? IIRC, the pain point was on larger sites if you did the pvxexe.config trick - it worked but required that all the users have 2018 workstation setup on their desktop. It was a workable solution for small sites but for 30+ user sites where only a couple people were testing it became cumbersome to suddenly have to load a new Sage 100 2018 to every workstation (even those not testing Sage 100 2018. If my memory is correct, once you move that 2018 pvxexe.config to the older versions then any workstation trying to log into the older version who doesn't also have 2018 workstation still has the problem Maybe this is something different?

That could definitely be the case - we're using it specifically for Test Upgrades, where folks are still using their prior Sage 100 versions in their daily work, but also doing testing on 2018. Prior to knowing we could simply replace the pvxexe.config, we were having clients set up totally different workstations to access 2018, so it didn't mess up Crystal in their daily life. Now we can use the same workstation to access those prior versions and to access 2018...

Related to this, during the BPAC meeting this past week, we mentioned that the Crystal version should be consistent across all product lines (100, FAS, HRMS, etc.). After a lot hemming and hawing, no one from Sage had a good answer. By the way, Jennifer Warawa in her presentation said they are striving to minimize or eliminate ""distractions"" that get in the way of us selling software. Last time I counted, I have at least 2 hours of distractions on the part of Sage every day. Of course, most of those emanate from Sales Operations . . .

Did she elaborate on what ""distractions"" have been subdued? Or are they just ""trying""? As I have been told, the road to hell is paved with good intentions.....

None were mentioned specifically. The next day when Larry Sunderlin did his presentation (or ""Lawrence"" when I'm really perturbed at him), there were so many ""distractions"" brought up, I lost count. Suffice it to say, Sales Operations is just one big ""distraction"".

Will be interesting to see how next progresses. Get your orders in early.....

I have no issue with Larry Sunderlin. He does the best he can with what he is given by top management. Larry chips away at the inefficiencies a little at a time, but what is required is drastic, immediate action. I don't sense NA top management is prepared to do that, because their strings are still being controlled by the UK. This was implied in many conversations I had during BPAC without anyone saying it directly. The UK still only cares about the share price and simply does not understand the US market.