Custom Programming
Dynamics TechBrief
MSSQL Deepsearch

How these can help you

How to purchase

Free Dynamics GP Sql Scripts


How these products can help you..


* GP Dissection / Technical Brief


1. As already mentioned in the home page and in the product description, our technical document can help you as a programmer to create customized modules, extensions, or add-on stand alone programs that directly manipulate Great Plains Dynamics database.


2. As a Dynamics GP database administrator, you can use the knowledge you will get from our documentation to construct quick SQL commands to make manual corrections in your Dynamics GP database. These commands can range from manually inserting records, updating records, or correctly deleting offending records or rows.


3. As an advanced Dynamics Great Plains user, you need to know what goes on under the hood. It is always a great idea to know and familiarize yourself with those technical details in order to maximize your output in using Dynamics GP.


4. If you are an aspiring IT practitioner that wants to get Microsoft certifications, then having these set of information is a definite advantage.


5. Generally, all Great Plains Dynamics users can benefit from more technical knowledge of the product. Have you checked lately how financially rewarding it is to be a Dynamics Technical expert or consultant? Trust us, it's a great position to be in.


* Our MS SQL Deep-Search program is a great handy tool for debugging your custom GP Dynamics programs. It can deep search ALL ROWS, ALL COLUMNS and ALL TABLES of your database to find corresponding matches for the data you are looking for. Now you'll be able what exact table and/or column actually holds that particular data!




1. Sample scenario of how Deep-search can help you in developing a custom module for Dynamics GP:

    Let's say you want to develop your own custom program or add-on module that will automatically create a customer record into Dynamics database. To do that, you need to be familiar with what physical tables are actually being populated when you add a customer record via the normal Dynamics process.


First you need to figure how Dynamics is doing that process by performing a normal Dynamics procedure and then immediately running Deepsearch afterwards to trace the database changes. As a simple test, create a new record like you would normally do in Dynamics. For example customer name "NEWUSER ABC", with Customer Code "100123". After creating that new customer, run Deepsearch and search the name value "NEWUSER ABC" or the customer code value "100123".

  Deep-search will then reveal to you each table and column name that contain those values and now you will have a clearer idea what Dynamics did behind the scenes.


It's more like REVERSE-ENGINEERING the process. In a typical SQL tool, you give it the tables and columns to access the unknown rows of data. With Deepsearch it is the opposite -- you give it a sample row of data and it will give you the correspoding table and column names.


2. Deepsearch is a "must tool" when cleaning up records that can not be done by Dynamics alone, here's why/how:

    There are times when you need to remove erroneous records or rows in your Dynamics database via SQL script. These rows are the results of invalid DYNAMICS shutdown, human error, or caused by just plain undocumented bugs lying inside Dynamics program. Let's face it, these strange things happen in Dynamics. Most of the time, these records cannot be removed by the built-in deletion commands in Dynamics and the only way to remove them is via SQL script.

Example 1: An erroneous CUSTOMER RECORD entry with a blank name, invalid dates, etc. Here, a common thing to do is to just delete the record from the main customer table RM00101. But wait.. did you know that there are other tables that may contain that invalid customer ID? When you delete the record only from the main customer table, you will leave a lot of orphaned records that will eventually cause a lot of mix ups in your database.


Example 2: An erroneous ORDER with other invalid fields like blank customer name, empty address, a null date, etc. In this situation, you will most likely delete it only from the Master ORDER table SOP10100 or the history table SOP30200. But what about the line items table SOP10200 and SOP30300? What if these erroneous records have existing entries in the "hold" table, lock table, etc.?


How can you totally remove those invalid records?


Well, you can, but only if you know where they are, right? You can use Deepsearch to locate all the entries where that invalid customer or order record with surgical precision. When you are able TO FIND ALL offending records, there there is so much less chance of leaving orphaned or abandoned records hiding in other tables which could cause later problems.




Note that our MS SQL Deep-Search program works not only with a Dynamics GP database. It will work with any MS SQL database, version 7, version 2000 or SQL Express.



GP Techbrief

Format: Zipped installer file



DeepSearch program

Format: Zipped installer file



GP Techbrief + DeepSearch program
Discounted Cost:

Format: Zipped installer file




Trademarks: Microsoft™, Microsoft Dynamics™ and/or Microsoft logos, products, and services referenced in this site are either trademarks or registered trademarks of Microsoft Corporation.

Disclaimer: This product is not officially endorsed by Microsoft. Furthermore, this website does not imply representation of Dynamics™ or relationship with Microsoft in any form.