Dynamics GP uses OPEN, WORK and HISTORY tables to process transactions. As transactions move between the tables, interruptions (much like those that cause stuck batches) can cause duplicate data to be left in one of the tables. These scripts identify the duplicate transactions if you have any. Once you know which documents have duplicate entries, you can dig deeper into the tables to find out which record is the correct one.
-N.B. Duplicates often have missing data in the columns or are missing their corresponding line entries.
This script can help with the following error code: "The stored procedure createSQLTmpTable returned the following results: DBMS: 2627, Microsoft Dynamics GP: 0."
Benefits of using SQL Scripts
Dynamics GP is a great system full of lots of features, but every now and then we need to turn to SQL to help us. So we have gathered some of the most useful SQL scripts from our partners, and the GP community, for your use.
Save time on tasks by batch processing them
Take the initiative and start solving your own support cases
Safely maintain your system and keep it free from bad data
Automatically run these scripts overnight to preserve your performance
Microsoft Dynamics GP easily integrates with one of the world's most used applications, Word. Together, it is possible to create beautiful looking reports that can seamlessly flow from Dynamics GP. Al...
Sometimes when testing a new GP system, you need to assign items to vendors, and want to avoid having to do so on an individual basis. This script allows you to do just that. Add all items to all vend...
We’ve all been there! We meant to store the system password in a secure place just in case we forgot it, but that didn’t happen. And now we are locked out of all of the Dynamics GP system menus. What ...