This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
While I am updating examples, I have made some changes to the Adding Window Size and Position Memory using the Support Debugging Tool sample code.
The original version used the Dex.ini to store the window size and position as a setting, for example:
The problem with this method is that it does not work well for a Terminal Server or Citrix based system (especially when there is a farm of servers). In this situation the settings are shared between multiple users and can differ depending on which server a user connects to.
So, I have updated the Support Debugging Tool Non-Logging Triggers to store the settings in the SY_User_Object_Store (SY90000) table instead. Now the settings are stored per user per company and will follow the user regardless of the workstation or server used.
The updated Support Debugging Tool Debugger Settings file with these triggers is attached as an archive to the bottom of this post.
Let me know what you think of the update.
For some related window size and position posts, see the following articles:
- VBA – Screen Size and Position Example
- Adding Window Size and Position Memory using the Support Debugging Tool
- Update: Adding Window Size and Position Memory using the Support Debugging Tool
- Why can’t I maximize my window?
- Where has my Microsoft Dynamics GP window gone?
14-Sep-2012: Added missing attachment. oops.
09-Oct-2013: Added links to related articles.
This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.