Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
In my previous post, I mentioned that I was assisting a developer with an issue. It turned out that the issue he was having was not the cause of an error, but the result of a previous error that the users had not told him about. Once the original error was fixed, the entire problem was solved.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Useful SQL Scripts Series.
Because Microsoft Dynamics GP is designed to have separate tables for WORK, OPEN and HISTORY transactions, there are times where it is possible for a transaction record to exist in more than one table. This is usually the result of an error or interruption.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Useful SQL Scripts Series.
When a system has a batch that is stuck as marked to post or a transaction that cannot be accessed as it says it is already being edited, the usual instructions are to exit all users from the system and then delete the contents of the activity tracking, and Dexterity session and lock tables.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Useful SQL Scripts Series.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
After the success of the Microsoft Dynamics GP Application Level Security Series, I have decided to release a another series which contains some really useful SQL scripts I have collected over time.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Over the years, the question of how to interact with the Microsoft Dynamics GP OLE Notes from outside the application has been raised many times.
I have responded to newsgroup posts with information that would hopefully lead the developers in the right direction.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Microsoft Dynamics GP Application Level Security Series. This is the final article in this series at this time.
Microsoft Dynamics GP version 10.0 introduces a new pessimistic task and role based security model. This new model has a completely different table structure to the previous optimistic user and class based security model. Which means that when upgrading the security settings cannot just be transferred across.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Microsoft Dynamics GP Application Level Security Series.
When attempting to open a window you might receive the following error message:
Cannot access this form because the dictionary containing it is not loaded.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Microsoft Dynamics GP Application Level Security Series.
When access is denied by the application security system to a window, you will receive the following error message:
You don’t have security privileges to open this window. Contact your system administrator for assistance.
Sometimes, the window you expected to open does not, which probably means that the security on that particular window needs to be changed. Other times the window still opens even after the security error, which probably means that a hidden system window failed to open.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Microsoft Dynamics GP Application Level Security Series.
When logging into Microsoft Dynamics GP or Microsoft Business Solutions – Great Plains, you might receive the following error:
You don’t have security privileges to open this window.
Once you click OK, the login appears to complete.