Update: Adding Window Size and Position Memory using the Support Debugging Tool

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:

MBS_Win_POP_PO_Entry_POP_PO_Entry=-400,-118,664,456

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?

David

14-Sep-2012: Added missing attachment. oops.

09-Oct-2013: Added links to related articles.

Debugger Settings POP Entry Window Size.dbg.zip

Comments

• Anonymous
  August 21, 2012
  This is fantastic - thank you David!

• Anonymous
  September 09, 2012
  Posting from Mark Polino at DynamicAccounting.net msdynamicsgp.blogspot.com/.../update-adding-window-size-and-position.html

• Anonymous
  September 01, 2015
  Hi Dave,  I am new to using the Support Debugging Tool and wanted to try it for the purpose described in this article.  I am having problems importing the configuration XML into my test environment.  From the Configuration Export/Import screen, I navigate to the file and click on import.  The next window says that there are "No Objects to Import"  I am using the version 14.00.0020 of the GP Power Tools.  Do I need to modify the XML file for it to work with this version?  

• Anonymous
  October 01, 2015
  Hi Medardo Please download GP Power Tools again from the Mekorma site. There was an issue found with importing xml files from the SDT into GP Power Tools. It has been fixed. https://winthropdc.wordpress.com/2015/09/04/gppt-gp-power-tools-build-20-hotfix-2-released/   David