Do you have Windows Text size set to a value greater than 100%?

Open Sage 100 on you Primary Monitor, select the maximum scaling option available - Drag the Sage 100 Launcher to your secondary monitor.  Is the screen outside the bounds of the display? 

My client was runnng in the 1600x900 and 125% mode prior to this update and was working perfectly at medium.  This is why I am suggesting the need for an override capability where the automatic metrics are erroneous.

I do not.  It is set at 100.

Secndary monitor has more than twice the resolution of the primary so Sage looks tiny on it.

1600 x900 with Text Size 100% should enable Default and Medium.

Open Sage 100 on you Primary Monitor, select the maximum scaling option available - Drag the Sage 100 Launcher to your secondary monitor.  Is the screen outside the bounds of the display?  Additional scaling options should be available.

On your secondary monitor at resolution 3440 x 1440. You should have an Extra Large Scaling option available.  

With primary monitor at 1600x900 100%  I have default and  medium.  Check.

Drag the window over, it is not outside of the bounds.

Made my 3440 x 1440 monitor the primary and I have default - medium - large.  No extra large.

Oddly enough though when I checked - it looks like scaling was at 125% on the 3440?.   Possibly the scaling can be different on each monitor?  Switching the setting and rebooting to verify.

However it appears that it is still taking it's cue from the primary monitor.

My extra large monitor is using HDMI,  the medium sized monitor is using VGA,  I assume that the built in monitor to the notbook is VGA also.   Maybe that has something to do with it.

Tom, from my experience, Sage 100 2017 and PU1 allowed the application scaling for non-Sage 100c clients.  It's a nice "extra" and my clients loved it.  Now, I just need to know how to bring that functionality back for the clients on 2017 PU2.

After much experimentation,  I'm going to confirm that the system is taking its cue for determining what scalings are available from the primary monitor in a multi-monitor system.  Draggin Sage from one monitor to another has no impact whatsoever.

Hi John,

I've also been told by support that we should use classic desktop with non-C installs (and in KB's like the last bullets in the below), but it sounds like we can use standard for non-C?

Sage 100 2016 opens in "Standard Desktop" view even though feature is not enabled

• Sage 100 2016 opens in Standard desktop view
• Unable to select task on new Sage 100 desktop
• Sage 100 opens in Standard desktop view even though feature is not enabled

• Corrected on Sage 100 2016.1 update

Download Sage 100 2016 Product Update 1
LM5013-T: "Sage 100 has stopped working"

Possible Workaround:

1. Browse to user's Documents folder (C:\users\username\Documents)
2. Rename 'Sage 100' folder
3. Open Sage 100
4. Select 'The classic desktop'
5. Select OK

• Standard Desktop View is only available in Sage 100C
• Sage 100C is available to customers purchasing a new subscription support plan

105263



ID:70426Last Modified Date:8-5-20161470404948777  

Hi, This issues noted in the KB should all be resolved by the latest PU. The 2016 release was restricted to only allow "c" users access to the new launcher (Standard) and launcher features. There was a workaround that allowed some users around the restriction and access the new launcher (standard). The workaround generated this KB.

For those users on 2016 non "c" they are limited to the Classic Launcher. I will double check to ensure this has not changed.

The launcher restrictions in the 2016 release were removed with the 2017 release. In the 2017 release "c" and non- "c" user have access to the new Launcher (Standard).  There is a sub set of features in the new Launcher (Standard) that only "c" users have access.

Hope this helps clarify.

Thx John Nichols

Sage