The Dynamics GP Blogster

Back in January of 2009, I wrote an article showing a method of calling a SQL Server stored procedure from Dexterity by calling a stored procedure prototype script (sproc) in sanScript. See,  Calling SQL Server stored procedures from Microsoft Dexterity  (January 26, 2009). This sproc tells the runtime engine (Dynamics.exe) that it must connect to either the system or company database to run the stored procedure of the same name. I particularly like this method because it basically it shields the developer from dealing with connections, etc. Also, the procedure executes under the user's security context. However, there are times when it is necessary to go the extra mile, especially if you have to call procedures you do not want to prototype into your code as a sproc - case in point, calling third party stored procedures, or eConnect stored procedures. Enter the use of Dexterity SQL library functions and pass-through SQL. The Dexterity SQL library functions are well doc...