Following on from my previous post: Solving Performance Problems with Microsoft Dynamics GP and Windows 10 – Part 1, I was still not happy with the performance of Dexterity and Microsoft Dynamics GP on my newly updated Windows 10 development machine.
This article takes you through the steps to get your Dexterity and/or Dynamics system running fast on Windows 10.
Now that I am running Windows 10 and am starting to get back to work with developing for Microsoft Dynamics GP and Dexterity, I have been noticing some serious performance issues.
This article takes you through the steps I used to identify the issue and what I did to resolve the issues. After making the changes listed in this and the next article I am happy with my Windows 10 development environment.
Today, I was contacted by a fellow Dexterity developer who was having trouble getting Dexterity for Microsoft Dynamics GP 2015 or later to run Dynamics.dic in Test Mode.
In this article, I will take you through the errors you could get and how to resolve them. Some of these you might know from previous versions, others are new to GP 2015 or later.
Part of the #Dexterity Development Environments Series. See Summary at end for quick list.
This is the third and final article in the series, make sure you look at the previous articles before this one.
The previous articles can be found at:
Today’s article adds the final step by adding a method for a user to execute the code we have written so far without requiring access to any Support Debugging Tool windows.
This is the second article in the series, if you haven’t already, please see the previous article: Using the Support Debugging Tool to create user accessible SQL Scripts – Part 1.
Today’s article adds a simple user interface for the previously created SQL scripts using Dexterity sanScript.
It has been a while since I have posted a technical article on the blog. This is because I am spending almost all my time working on bringing some existing and new products to market.
I am still working on the rebranded and improved release of the Support Debugging Tool. There will be a number of improvements in its features and navigation, more on that soon.
For now, I wanted to post a really clever method of using the Support Debugging Tool to provide additional functionality to end users.
It has been many years since my BlackBox game got a mention and so I thought it was time to bring it up again.
I first wrote the game BlackBox for Dexterity in 1999 while I operated as Winthrop Dexterity Consultants. The game is based the original board game by Eric Solomon and was created with his kind permission.
Following on from my last post, Customising the Company Login window series – Visual Studio Tools revisited – Visual C#, where I completed the Customising the Company Login window customisation using Visual Studio and Visual C#, I wanted to create the same example using Visual Basic .Net.
Thanks to Tim Wappat from the Dynamic Coding Blocks blog for his post which helped me get past the issues I was having accessing the Continuum Integration Library:
Just before I left Microsoft, I was writing a series of blog articles about Customising the Company Login window so that you could see the full company name in the drop down list for long company names.
I had shown how to achieve the customisation with Dexterity and with Visual Basic for Applications, but was having problems getting it to work from Visual Studio Tools.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
It is time to release a new build of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I had an interesting case where a Dexterity Developer was having trouble getting some code to update a range of records selected in a table. The code would only update the first record in the range.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
GP Power Tools – Administrator Tools Module can provide this functionality without needing customizations. (http://WinthropDC.com/GPPT)
Following on from my previous posts: Customising the Company Login window series Part 1 – Introduction and Customising the Company Login window series Part 2 – Visual Basic for Applications, here is the method to create a solution using Dexterity.
This is a reposting of an article Alice Newsam originally wrote on my Developing for Dynamics GP blog.
Hello, my name is Alice Newsam and I am software engineer on the Dynamics GP team focusing on Dexterity and I have a question for you:
Have you ever thought to yourself while working in Dexterity “I know there’s a .NET class that does this. It would be handy to access that right about now.” or “If only I could increase the string size to hold that data.”?
Well read on because you’ll be excited to learn about a feature that the GP Development team is currently working on for the GP 2015 release: .NET Interop.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
GP Power Tools – Administrator Tools Module can provide this functionality without needing customizations. (http://WinthropDC.com/GPPT)
Recently a comment from David M (not me) was posted on the Support Debugging Tool Portal page asking:
“We have some fairly long names for our GP companies. Well, when logging onto GP, the second “Company Login” screen cuts off the company names too short for us. The entry field for companies allow for longer strings (65 Characters) but only displays 31 characters on the pull-down list. There is plenty of real estate on this window going unused. Can anyone think of a way to enhance/fix this to display more of the company name?”
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
A customer ran across an interesting issue with Excel Based Budgeting after they upgraded to GP 2013.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
It has been a way too long between releases, but I am finally ready to release Build 18 of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0).
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This will be a 2-for-1 post today as the example given solves a frequently asked question and was used to solve a customer issue.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I had a case today where a developer was having issues when using the Customer Combiner. This functionality was part of PSTL (Professional Services Tools Library) and as of Microsoft Dynamics GP 2013 Service Pack 2 is now part of core code.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I came across an issue where a feature in Microsoft Dynamics GP would work when the workstation had its regional settings set to United States, but would fail to produce any data when the workstation had its regional setting set to Australia, New Zealand, United Kingdom, etc.
Winthrop Development Consultants Blog 