Click here to
Subscribe to
our Newsletter
Development related Posts
This is repost of an article I wrote for the Knights of GP Blog. It explains the performance issues with using Microsoft SQL Server 2025 with Microsoft Dynamics GP and how to resolve them.
Here is the link to the original article on the Knights of GP site:
If you’ve ever needed to change an existing Customer ID or Vendor ID you would have found that there are tools available, but if you need to change the Address ID values for addresses associated with Customers and Vendors, you would you would be in for an arduous, manual, time consuming task as there are no tools available.
This article provides free sample projects that add these tools to Microsoft Dynamics GP using GP Power Tools – Developer Tools module. The code can be downloaded and installed easily.
After the release of Microsoft SQL Server 2025, we are now starting to see customer sites implementing the new version in their Microsoft Dynamics GP environments.
So far, I have been notified by two customers, that I work closely with, that they are having issues with Dynamics GP performance being slower on the SQL Server 2025 than their previous SQL Server version.
The following information on the issue and a solution has been provided by my colleague and friend, Arthur Achilleos, with a call out to Rob Farley MVP (who assisted Arthur’s troubleshooting).
In this article I will explain the theory and initial code to get a Lego Spike Prime robot following a wall.
Disclaimer: This article will use Robocup Junior Australia‘s Rescue (Maze) Challenge with a Lego Spike Prime robot as an example.
At the end of the second article in this series, I mentioned some additional line following methods. In this article I will explain the theory and initial code to get a Lego Spike Prime robot following a line.
Disclaimer: This article will use Robocup Junior Australia‘s Rescue (Line) Challenge with a Lego Spike Prime robot as an example.
If you have not read the previous articles, please do so before continuing:
Recently an issue came up on a customer’s system and today another customer had a similar issue. I thought it would be worth writing it up on the blog to help others who come across it.
The issue is an error when attempting to save data within Microsoft Dynamics GP resulting in a dialog in the form below:
Unhandled database exception: A save operation on table ‘XXXX’ (45).
This is the seventh article in the series on making window fields required. If you have not yet read the introduction article to the series, please read that first:
This example uses GP Power Tools to make the Reason Code field on the Item Transfer Entry Scrolling window required. This article was prompted by a support request that came in today.
Visual Studio Integration Toolkit provides Application Programming Interfaces (APIs) to Visual Studio Tools for Microsoft Dynamics GP developers adding functionality that is normally only available to Dexterity developers.
For almost 20 years the application menus feature has been available at no charge as Menus for Visual Studio Tools from Microsoft and later Visual Studio Integration Toolkit from Winthrop Development Consultants. This was David Musgrave’s gift to the Microsoft Dynamics GP community. Sadly, as the cost of maintaining and supporting the product increases, it has become necessary to charge a small fee for subscriptions starting in 2027.
Do you want to customize Microsoft Dynamics GP or have customizations that you want to support into the future? Now is your chance for both customers and partners to get trained in Dexterity, the development environment that Dynamics GP is built on.
Understanding Dexterity will help any developer working with Dynamics GP regardless of the development environment they end up using. This knowledge is vital for developers using Dexterity, Visual Studio Tools (C# or VB.Net), “End of Life” Visual Basic for Applications (VBA) or using the GP Power Tools – Developer Tools module.
I will be running the 5-day Dexterity Fundamentals for Dynamics GP bootcamp training class in the week before the Community Summit conference in Nashville, Tennessee, USA in October. Please register for the training now and plan to be in Nashville for the week before the conference.
Recently, Mike from Thybar Corporation contacted me about an issue he was seeing in Microsoft Dynamics GP v18.7 with General Journal document attachments.
Journal Entry attachments that had been added before upgrading Microsoft Dynamics GP to v18.7 could no longer be viewed from the Journal Entry Inquiry window after the upgrade.
This article is an update to previous articles about errors on temporary tables when using Microsoft Dynamics GP. We have seen a recent increase in issues of this type as well as a misunderstanding of what is happening to cause the issues.
The issue shows as a dialog with a message like:
An open operation on table ‘MBS_sySecurityView’ failed because the path does not exist
An open operation on table ‘WDC_Field_Security_Tag_TEMP’ failed because the path does not exist
An open operation on table ‘IV_Reconcile_PO_TEMP’ has an incorrect record length.
The name of the table can vary but the examples above include a couple of common ones from products I created, being GP Power Tools and Field Level Security (Advanced Security). However, this issue is due to the Windows environment and has nothing to do with the Dexterity product or SQL Server.
Here is an awesome update to the previous sample customization which added 6 Additional Item Category Fields:
This update makes the following improvements, but does need at least Build 32 of GP Power Tools to work:
Community Summit 2026 will be held at the Gaylord Opryland Resort in Nashville, Tennessee, USA from 11th October 2026 to 15th October 2026. I am again planning to offer Microsoft Dynamics GP Development Training during the week before the conference. Please respond to the survey below to register your interest and preference for what training class should be run.
Update: The 5 day Dexterity I course and the 1 day GP Power Tools workshop have been selected.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 3 of 3 in the series.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 2 of 3 in the series.
Over time the amount of data stored by your Microsoft Dynamics GP system can get quite large. Without buying new hardware, there is a simple way to make your system faster and decrease the space used to store your databases.
This is where a couple of the features of the Database Module of GP Power Tools come in to help. This is article 1 of 3 in the series.
When GP Power Tools Build 32 was released, it added powerful Custom Table functionality which allows for a developer to create a custom table definition and have that table created in each company automatically. The table can then be used in a similar fashion to a native Dexterity table using a suite of Custom Table Buffer Helper Functions.
This article updates the original article (below), which explained how to create a Custom Forms Module demonstration project, to use Custom Tables instead of SQL Tables for a much faster and simpler implementation.
Welcome to the eleventh article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will show how to use Custom Tables (added in Build 32) to store data rather than the DUOS table. In the previous articles we included the Customization Maintenance packages and showed how to use manual SQL tables.
Welcome to the tenth article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will show how to use manual SQL tables to store data rather than the DUOS table. In the previous article we included the Customization Maintenance packages. In the following article we will show how to use GPPT Custom Tables (even better than manual SQL tables).
Welcome to the ninth article as an update to the series of articles that explains in detail the steps to add a user defined custom field to a window using Modifier, Report Writer and GP Power Tools to add the business logic.
The series should be read in order starting with the introduction article:
In this article we will provide updates to the project adding the modified window and report to the project. In the following articles we will show how to use manual SQL tables and then GPPT Custom Tables (even better than manual SQL tables).