The Dynamics GP Blogster

Rarely you will hear the Dex.ini file being called the Microsoft Dynamics GP defaults file. However, the Dex.ini contains keys (and their associated values) that define how Microsoft Dynamics GP behaves in some cases. For example, SQLLastUser=sa stores the login of the last user who accessed the system on that specific instance of Microsoft Dynamics GP, in this case, 'sa'. Likewise, AutoInstallChunks=TRUE, allows Microsoft Dynamics GP to bypass prompting the user for new code (chunk file) to be installed at the time of launching the application. There are other settings controlling how certain features behave. You can find a list of Dex.ini settings here . Recently, I was helping a good friend of mine up in Maine who attended my Dexterity class in Boston and this time he wanted to know how to read the path for the Microsoft Dynamics GP help file. Of course, there's a simple (predefined) method for this as my good friend Patrick Roth with the Escalation Engineering team...

In past weeks I posted an article explaining how Microsoft Dexterity could benefit from IntelliSense technology and enter a request for the community to vote on the Microsoft Connect product suggestion 570553 so the feature could be considered by Microsoft for introduction into a future release of Microsoft Dexterity. You can find the link to those articles, as follows: Dexterity and IntelliSense Dexterity and IntelliSense: It's time to vote! A couple weeks later, the answer came from the Community after Tim Gordon , a software developer and consultant with Alpine Limited saw the post referencing my articles over at Developing for Dynamics GP . Tim contacted David Musgrave, who then copied me after the first couple exchanges they had. Tim had been working on a very rudimentary prototype of IntelliSense for Dexterity. His Visual Studio IntelliSense application sits in the Windows system tray "listening" for a Dexterity process. When Dexterity becomes available, the appl...