Sage 100

Upgrading from 4.40 to 2014 and running into initial screen focus issues. Example, open Inventory Maintenance screen, you have to right click on the Item ID to force the focus to shift to this screen. Happens on login too - focus should start with login ID but you must right click the ID then shift to the keyboard to type.

Did you run the Update Custom Panels to Current Level from Custom Office?

Yes, @MoiraGoggin I did. I'm also noticing that screens are open behind the main menu so I switched to ribbon bar so I could find the screen. Good grief.

It might be the Windows display. It must be 100% (smaller).

I'm using a RDP connection and am unable to adjust screen setting.

Found this, might help - change the keyboard setting for the rdp file to ""On This Computer"". This is found under Local Resources when you edit the rdp file.

Thanks! I'll give this a try tomorrow and report back.

Good news. Thanks to @MoiraGoggin I now have the cursor active.

I tried changing to 'On this computer' and it worked for a while and then reverted back. Any other ideas? We don't have that problem at our office, only at some of our clients.

I think I found a Sage KB article - will report back whether this works.

Sage KB info to correct 'screens opening in behind' From the Windows Desktop, open Start, Run In the Run field (or in Search programs and files) type REGEDIT and press the Enter key to open the Registry Editor Expand HKEY_CURRENT_USER, Control Panel, Desktop While Desktop is selected on the left pane, the right pane of the Registy Editor window should display all associated keys Browse through the list select Control Panel ->Desktop -> locate and highlight the ForegroundLockTimeout key Double-click to open the ForegroundLockTimeout key In the Value data field remove what is there and enter 0 (Note: That is a number 0, not the letter O) Click OK Back in the Registry Editor window, click File, then click Exit Note: This is Windows user profile specific and will have to be done for each individual windows user experiencing the issue. The Administrator will have to modify ForegroundLockTimeout registry key value for each remote user. A Group Policy can be created for remote users that modifies this key for all remote users. This worked!