Click here to
Subscribe to
our Newsletter
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:
It’s not too late to join the next Community Learners Event and learn about what’s new in GP Power Tools.
Using real-life examples, this session will demonstrate how GP Power Tools can enhance your Microsoft Dynamics GP investment. Discover how it addresses your pain points and makes the “impossible” possible.
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).
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.
Everyone wants extra user defined fields on their Microsoft Dynamics GP windows. In the previous articles we showed how easy it is to add, modify and format the layout of extra fields using GP Power Tools with the new Custom Fields feature.
We thought we were done, but now the request has come through from the HR team to include the Pet related custom fields on the Employee report.
Everyone wants extra user defined fields on their Microsoft Dynamics GP windows. In the previous articles we showed how easy it is to add, modify and format the layout of extra fields using GP Power Tools with the new Custom Fields feature.
Now we have one final request…. The HR Team want to have the custom fields displayed on the Employee Inquiry window.
Everyone wants extra user defined fields on their Microsoft Dynamics GP windows. In the previous articles we showed how easy it is to add and modify extra fields using GP Power Tools with the new Custom Fields feature.
Now we have a yet another problem …. “Boss Level Scope Creep”….
Everyone wants extra user defined fields on their Microsoft Dynamics GP windows. In the previous article we showed how easy it is to add extra fields using GP Power Tools and its new Custom Fields feature.
Now we have a new problem …. “Scope Creep”. The HR department has realized that their employees might have more than once pet and so would need allow for multiple types of pets to be selected.
Everyone wants extra user defined fields on their Microsoft Dynamics GP windows. It is possible to add extra fields but there have always been compromises. Either it requires custom development with scripting and modified or alternate windows, or fields are in a separate window or sidebar, and the data is often stored in multiple records across multiple tables.
This year, as we celebrate 20 years of GP Power Tools, the upcoming Build 33 adds Custom Fields. This amazing new feature allows you to add almost any field to any window without any code or using Modifier.
This year GP Power Tools turns 20 years’ old, and we will celebrate by releasing Build 33 with many enhancements and new features and some fixes. The release of GP Power Tools Build 33 for Microsoft Dynamics GP v18.4 or later is planned for mid-year, once all the development and documentation is completed.
We are excited to tell you about one of the major new features … Login Control.
Winthrop Development Consultants is fully committed to the continued support of Microsoft Dynamics GP and its ecosystem. Our ISV products are only compatible with Dynamics GP and have been created to solve pain points and missing features as requested by the GP community.
While Microsoft has stated that they will cease support for Dynamics GP in 2031, it is important to note that “End of Support” does not equate to “End of Life”. There is plenty of life left in the product and, with the support of the community, GP will live on well past the official end of support. A driving force in the community support will be the Knights of GP.
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:
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.
I am finally getting back to work after travelling and presenting at Community Summit 2025 in Orlando and visiting family in the UK. Still got lots of tasks to catch up on but I wanted to write about the Knights of GP.
The Knights of GP is planned to be a community based co-op of customers, consultants, Independent Software Developers (ISVs) and partners who will work together after Microsoft stops supporting Microsoft Dynamics GP to allow the product to remain supported by the community who use and love it. Join us for the tomorrow’s Fireside Chat…