While importing a customised Form with VBA I encountered a problem and received a Component write exception;
Component Write Exception
The form itself had imported but the VBA element had not.
Not having seen this error before I hit up Bing and soon found a blog post from Dex Master David Musgrave where he discusses this exact issue on GP9 (I was loading a customisation from GP9 to GP 2010 to upgrade).
The answer was not quite what I wanted. I was hoping for something nice and simple, but instead I needed to export all the customisations, delete the forms.dic, reports.dic and dynamics.vba files and then reimport all of the customisations.
After I did this the import worked fine.
Fred Webb posted a question on the Dynamics GP Community Forum asking if it was possible to prevent the User Date being changed in Dynamics GP 2010.
One response was to use Field Level Security which would work but seems a little excessive. I had a think on alternatives and, because we’re dealing with GP 2010, the one I came up with was to prevent the User Date window being opened by using a little VBA.
The package for Microsoft Dynamics GP 2010, which also works for Microsoft Dynamics GP 2013, can be downloaded at the bottom of the post.
The VBA I used was:
Private Sub Window_BeforeActivate()
Private Sub Window_BeforeOpen(OpenVisible As Boolean)
Me.Hide causes the UserDate window to be hidden from the user as it starts to open, and Me.Close forces it to close.
I could have put both the Me.Close and Me.Hide in the sub Window_BeforeOpen, but I found the main GP window didn’t get focus back. By splitting the Me.Close into Window_BeforeActivate focus was returned to GP when the UserDate window was closed.
The downside of using VBA asa solution is that it will not work with the Microsoft Dynamics GP 2013 Web Client, although it will work with the standard 2013 client.
I was recently asked to assist the Support team to look into an issue with the Trail Balance Summary modified report. The problem was that when sent to screen or printer the report was fine, but when exported to Tab Delimited file, the columns didn;t match up with the totals at the bottom.
Trial Balance Summary on Screen shows as aligned;
In July, as part of his weekly MS Connect suggestion series, Mark Polino raised the issue of SmartList Favourites and the default Visible To which is set to System.
Mark’s suggestion was to have the default changed to User which would leave a generally tidier list. To be honest I’d rather have a setting which allowed the default to be chosen by each client. The reason for this is we’re currently in the middle of an upgrade project where a few Microsoft Dynamics GP systems will be merged into one and it would be good to have the default Visib le to set to Company.
Following on from my recent post on a fixed width SmartList left pane I decided to have a fiddle and see if I could force the default to something else. And it turns out with some simple VBA that you can do exactly that;
In July last year, Frank Hammelly posted a SmartList customisation for Microsoft Dynamics GP 2010 on his blog gp2themax.
I’ve recently been taking a look at Microsoft Dynamics GP 2013 and decided to see if I could use Modifier to reproduce this customisation for GP 2013 (I have no reason to believe the customisation posted by Frank won’t work with 2013, but I wanted to dabble with Modifer and this seemed a good starting point); the customisation can be downloaded at the bottom of this post.
The screenshots below show SmartList in both it’s default size and maximised with the left pane remaining a static size and the right pane occupying the rest of the window;
In 2009 Patrick Roth, on the Developing for Dynamics GP blog, posted a customisation for the Microsoft Dynamics GP login window which displays a message box if the caps lock is on when the user goes to enter their password.
Then, back in July, Aaron Berquist on his blog High Dynamic Range, posted an article on using VBA to create a desktop alert to users which doesn’t take focus away from the application.
I decided to take a look and see if I could combine these two ideas into one and have a desktop alert displayed when the user has caps lock on when logging in, which is far less intrusive than the message box approach by Patrick.
The result is a customisation of the login window (which you can download at the end of the post) to display an alert if the user has the Caps Lock on using the desktop alert code Aaron posted.
The code displays a message to the user if they have Caps Lock on when the login window displays, or when they tab into the Password field if they haven’t already seen the message;
The customisation was created in GP 2013 and has only been tested in this version of GP but has been tested on Windows Server 2008 R2 and Windows 8. As with everything I post here, it is supplied entirely without warranty and you use it at your own risk.
However, if you do have problems let me know and I’ll see what I can do to fix them.
One of the points I make (repeatedly until I see a confirmation they’ve done so) to clients when implementing Microsoft Dynamics GP is that they need to make sure that a maintenance backup of the SQL databases and other resources are being made.
In some cases the maintenance backup is a once a night job, other clients have had one done every twelve hours with log backups made every hour. As long as a regular backup is being made I’m happy and stop nagging them.
In the last post I showed how the FRx menu can be renamed to show Management Reporter instead.
However, it is also a per user setting so would need to be done for each user created in Microsoft Dynamics GP who had access to Management Reporter.
To make the job a lot less onerous, I thought it might be useful to follow up with a SQL script to copy the FRx command customisations from one user to all others Continue reading
One of the features introduced in Microsoft Dynamics GP 2010 was the Word templates which could be used instead of the Report Writer reports (known in 2010 onwards as Standard reports). There were several Word templates shipped out of the box with GP that could be amended quite easily but if you needed to use one of the others then a lot of work was needed to manually create the template from scratch.
In Microsoft Dynamics GP 2010 R2, the Word Template Generator, available as a separate download from PartnerSource (login required) was introduced which would generate the base Word template which can then be amended as required. Continue reading
I’m currently doing some work for a client where we’re modifying some of the reports in Microsoft Dynamics GP and I’m trying to avoid using Report Writer as a) I don’t like it, b) Word template reports look better and c) I don’t want to spend time training a client on a module which can be avoiding and is being retired in the near future.
For some of the reports such as the Sales Orders and Invoices and the Purchase Order reports, there are Word templates already available for customising, but for some of the reports such as the Sales Picking Ticket or Dispatch Notes there are no Word templates available by default.
In Microsoft Dynamics GP 2010 this meant starting a template from scratch. In Microsoft Dynamics GP 2010 R2 you can use the Word Template Generator to convert a saved xml report into a Word template.
The only problem is, I can’t find it. None of the blog posts I read announcing the feature said where it would be; just that it would be available with 2010 R2. My first port of call was within GP itself. The I tried the installation media but no luck. I then tried a couple of Internet searches and came up dry. I asked a colleague but they hadn’t used it before.
I finally searched on PartnerSource (I don’t like the PartnerSource search so usually try general Internet searches first) and finally found the download link for the Word template Generator.