This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A recent post on DynDeveloper.com caught my eye as I have faced a similar problem before and had to work quite hard to get the correct answer.
SQL
Support Debugging Tool Build 16 Hotfix released
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
It has been a while since Support Debugging Tool Build 16 was released back in January 2012.
While I have not been able to invest much time in adding new features to the Support Debugging Tool (SDT), I have been able to fix a few issues which have been reported by the community.
SQL Script for Account Level Security
This is a reposting of an article Sivakumar Venkataraman originally wrote on my Developing for Dynamics GP blog.
I recently joined Microsoft as a Partner Consultant for the Global Partner Services team. I have been associated for more than 8 years in the design, development and implementation of Microsoft Dynamics GP in India, Middle East and US. This is my first post in this blog and it feels great to be posting alongside community experts like David Musgrave, Patrick Roth and others.
Microsoft Dynamics GP offers the Account Level Security option to restrict the access of GL accounts to specific users. There is no specific report (or) Smartlist which is available for viewing the details of the accounts which each user has access to.
Understanding the Support Debugging Tool Series
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Welcome to a series of articles that are designed to help you understand how the Support Debugging Tool works and how you can leverage its different features. In the past, I have described features without explaining how these features can be used and what the differences between different modes is. With this series I hope to remedy that situation.
Continue reading
Controlling Support Debugging Tool Automatic Debugger Mode
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is the third in a series of articles that are designed to help you understand how the Support Debugging Tool works and how you can leverage its different features. In the past, I have described features without explaining how these features can be used and what the differences between different modes is. With this series I hope to remedy that situation.
Controlling Support Debugging Tool Manual Logging Mode
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is the second in a series of articles that are designed to help you understand how the Support Debugging Tool works and how you can leverage its different features. In the past, I have described features without explaining how these features can be used and what the differences between different modes is. With this series I hope to remedy that situation.
Understanding Support Debugging Tool Logging Modes
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is the first in a series of articles that are designed to help you understand how the Support Debugging Tool works and how you can leverage its different features. In the past, I have described features without explaining how these features can be used and what the differences between different modes is. With this series I hope to remedy that situation.
SQL Error: Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I resolved a very interesting case. We had a customer who had just upgraded from an early build of Microsoft Dynamics GP 10.0 to Microsoft Dynamics GP 2010 (11.0) and after the upgrade they were unable to save from the Customer Maintenance window.
How to format Microsoft Dynamics GP SQL Stored Procedures
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Have you ever decided to have a look at one of the SQL stored procedures in your Dynamics GP databases?
If you have, you would have noticed that they are extremely difficult to read. This is because comments and formatting white space are removed by Dynamics Utilities when it creates the stored procedures. This step was taken to improve performance of the resulting code, but has the side effect of making the code impossible to read.
Cross Linked Companies, Pathnames and Everything
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A long time ago, in an ERP system far far away, data was stored in tables which in turn were stored as files in folders.
Yes, before Great Plains Dynamics became Great Plains Dynamics C/S+ for SQL (version 3.15/3.17), we had to specify pathnames to dictate where the Ctree or Btrieve files for each series (Financial, Sales, Purchasing, Company, System, etc.) and for each product / dictionary would be located. There was also a location translation system which allowed the paths to be mapped when a workstation required a different drive letter or machine name to access the data.
Quick Tip: Dexterity SQL error invalid cursor state
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
In a recent case of mine, the ISV was running into a common issue that I’ve run into before more than a few times. Actually something I’ve done a few times myself.
The ISV was attempting to use pass through sanScript to populate a SQL temp table.
Quick Tip: Copying larger amounts of data in SQL Server quickly
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I recently posted the Quick Tip: Copying small amounts of data in SQL Server quickly. This quick tip used the clipboard to copy data between tables as an alternative to using DTS (Data Transformation Services), SSIS (SQL Server Integration Services) or Transact-SQL (T-SQL).
Troubleshooting Performance issues on a Wide Area Network
A while ago, I wrote a post: Why can’t I run Microsoft Dynamics GP via ODBC over a WAN? which discussed the reasons why Microsoft Dynamics GP will not work well when trying to use an ODBC (Open Data Base Connectivity) connection over a WAN (Wide Area Network). The post mentioned that the only support method for running Microsoft Dynamics GP in a WAN environment was by using Terminal Server.
With Terminal Server and its clients, all the processing is performed on the Terminal Server. The only processing handled on the client is drawing the screen and communicating with the Terminal Server. The communication between the Terminal Server and the client is just the screen data to be displayed and the keyboard and mouse inputs back to the server. If the Terminal Server is slow, processing will be slow and screen refreshing might be affected. If the connection between the Terminal Server and the client is slow, processing will be fast and only the screen refreshing will be slow.
Note: Citrix sits on top of Terminal Server and provides additional functionality. So when Terminal Server is discussed it refers to both Terminal Server with and without Citrix.
Quick Tip: Copying small amounts of data in SQL Server quickly
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I was working on a Microsoft Dynamics GP update case where we had to re-upgrade one company from the previous service pack to the current service pack.
eConnect error – The stored procedure doesn’t exist
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
I ran across an odd eConnect issue a while back that I thought I’d share today.
How to configure SQL Profile Tracing using the Support Debugging Tool
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Following the release of Build 16 of the Support Debugging Tool, I want to take you through how to configure the SQL Profile Tracing functionality so you can gain the benefits of this awesome feature.
The Support Debugging Tool has always been able to capture a DEXSQL.LOG of the communication between the Dynamics GP Application and the SQL Server, but when a Stored Procedure is called on the SQL Server, we lose visibility of what is actually happening at the SQL Server. Now with SQL Profile Tracing we can see exactly what is happening at the server as well and match this information with other logs we have at the user interface, Dexterity application and SQL Server levels.
Support Debugging Tool Build 16 released
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: The Support Debugging Tool is now GP Power Tools from Winthrop Development Consultants (http://winthropdc.com/GPPT)
A week into the New Year and no posts…. what’s happening? Read on to understand where all my spare time has been going….
After over four months of development, testing and documentation, I am thrilled to announce that build 16 of the Support Debugging Tool is now available for download from PartnerSource. This build has over 50 changes and focuses on functionality for logging and debugging issues with Microsoft Dynamics GP, while still having some improvements for the database or application Administrator.
Quick Tip: Working with VBA, Extender and Sales Transaction Entry
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have completed the development project I was working last week and have another Quick Tip that came out of the project. For the previous Quick Tips related to this project have a look at Quick Tip: Passing Variables to SQL Server and Quick Tip: Passing Date and Time Variables to SQL Server.
Quick Tip: Passing Date and Time Variables to SQL Server
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As a follow on from yesterday’s post, Quick Tip: Passing Variables to SQL Server, I wanted to discuss the related topic about passing of date and time variables.
Quick Tip: Passing Variables to SQL Server
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Wow, the week is almost over and I am yet to post something.
This week I was working on a small development project using Visual Basic for Applications (VBA) to execute some commands at the SQL Server level after some user interface events. The code to be executed needed to have values from the windows passed through to the Transact-SQL. Now most people just write the code and pass through the value of a string field concatenated before and after with single quotes.
sqlstring = "select * from IV00101 where ITEMNMBR = '" & CStr(ItemNumber) & "'"