This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have had a number of support cases and newsgroup posts recently about Customization to the Cash Receipts (RM_Cash_Receipts) window failing to work for Microsoft Dynamics GP 2010 when they worked for previous versions.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is a follow up post to my earlier post, which demonstrated how Report Writer when combined with the power of Visual Basic for Applications (VBA) was able to create a customisation that would not have been possible with Report Writer alone.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A few months ago, I worked on a support case where we needed to add a barcode to a Sales Order Processing transaction print out. We were able to achieve what we needed using Visual Basic for Applications (VBA) to handle some of the scripting for us. I have been meaning to write a blog post on how to make a customization like this for a really long time and have finally got around to it.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Alright, maybe I am stretching the truth a little, but I do get frustrated when people discount the Dynamics Report Writer as a useful tool. [Edit] I am not biased at all…. honest.
This is a reposting of an article Beth Gardner originally wrote on my Developing for Dynamics GP blog.
This is a follow up to my previous post on the VBA6.dll not found error (for 64-bit). I have found this can occur on 32-bit computers and Microsoft Dynamics GP 10.0 and GP 2010.
[Edit] Re-installing the VBA 6.4 core components (as used by Dynamics GP) has been shown to resolve this issue for VBA6.DLL, VBE.DLL, VBA7.DLL and VBE7.DLL errors. Please download the necessary files from this link:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Have you ever used Modifier and Visual Basic for Applications (VBA) to add an additional field to a window? Have you then had the issue when navigating through records on that window, it keeps coming up and asking “Do you want to Save, Discard or Cancel?” or “Do you want to Save, Delete or Cancel?“.
This is a reposting of an article Beth Gardner originally wrote on my Developing for Dynamics GP blog.
We have been running into a few different issues with Microsoft Dynamics GP 10.0 and GP 2010 when you have Office 2010 installed.
[Edit] Re-installing the VBA 6.4 core components (as used by Dynamics GP) has been shown to resolve this issue for VBA6.DLL, VBE.DLL, VBA7.DLL and VBE7.DLL errors. Please download the necessary files from this link:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I discussed an issue where Currency values returned by VBA to a report are multiplied by 10 or 100. To workaround the issue we used string calculated fields rather than currency calculated fields on the report and formatted our values with the FormatCurrency() or FormatNumber() functions (depending on if we wanted the currency symbol or not).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I wanted to highlight an issue that you might see when working with Visual Basic for Applications (VBA) and Report Writer.
The issue occurs when using VBA code to return a currency value to be displayed on the report and it appears to be randomly multiplied by 10 or 100. This is a known issue (Problem Report 59380) and this post should help explain what the problem is and provide an alternative solution.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
You might remember last month when we had a support case where the customer wanted to use Extender additional information against the General Ledger Journal Entry (GL_Transaction_Entry) distribution lines.
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 posts which are are designed to help Dexterity developers as well as VBA and Visual Studio Developers to understand how to work with passthrough Dexterity sanScript. The main focus of this series is to understand how to change the Dictionary Context that the code executes in.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
Honestly, I struggled a bit on the title of this article.
Is this article to show one way to use a Dynamics GP lookup window in your Modifier/VBA customization? Or is it an article that shows a way to work around the circular reference problem that you can get yourself into when using VBA across projects in Dynamics GP?
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Time and time again I have heard consultants say that the solution to stopping Microsoft Dynamics GP remembering the last user on a Terminal Server or Citrix installation is to make the Dex.ini file read-only. There was even a Knowledge Base (KB) article that suggested clearing the SQLLastUser setting from the Dex.ini file and then marking the file as read-only. Well, in my opinion this method has always been evil and from Microsoft Dynamics GP 10.0 onwards will not work anyhow.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I had a support case that was asking about errors when importing a package via Customization Maintenance (Microsoft Dynamics GP >> Tools >> Customize >> Customization Maintenance). The partner was unable to find an explanation of the errors on the Internet and so I thought I would explain what the errors mean and provide some best practices to avoid these issues in the future.
Continue reading
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week I had an interesting support case that I thought I would share with you.
The customer had created an Extender window to capture additional information for distribution lines on the General Ledger Journal Entry (GL_Transaction_Entry) window. The unique identifier for a distribution line is the Journal Entry field from the main window and the Sequence Line field from the scrolling window. These are the fields used when creating the Extender settings for the additional information to be stored.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A recent support case asked “Why can’t I maximise my Payable Transaction Entry Distribution window?”. This worked for versions 8.0 and 9.0 but does not work for version 10.0 and GP 2010 (v11.0). What has changed?
Everything. Well … lots in the way windows in the Microsoft Dynamics GP application are handled.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I was recently asked about a forum post of mine from a few years ago. It was about how to call a Dexterity report from Visual Basic for Applications (VBA). I checked the blog and could not find a post that showed the code in its simplest form. So here one is…
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I was recently asked to assist a colleague with an Extender case. The problem was that Extender data was not being removed from the Extender SQL tables when its parent record was deleted.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
A question came up a while back where the user wanted to know what company the user was logging into in order to give them a message depending on the company selected.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
I think the most customized window in VBA must be the SOP Entry window.
If the customization is not saving custom data for the header/line items, then it is adding custom logic based on document type and any number of other factors.
In all of this – especially saving custom data to a parallel table – the SOP Number is important as it identifies the document. And, of course, to be unique your primary key would also include the SOP Type field – just like the SOP10100 table does in Dynamics.
Getting the SOP Number is easy – it is the string value from the window.