Tag: Microsoft Dynamics GP 2010

While importing a customised Form with VBA I encountered a problem and received a 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.

I was recently on site with a client doing an upgrade from Microsoft Dynamics GP 2010 to 2013 and implementing Management Reporter 2012 to replace FRx 6.7.

The upgrade of Dynamics GP to 2013 went through without issue, once I sorted out the overlapping periods which are no longer allowed (I hope Microsoft will be updating the exam question), but I ran into an issue with Management Reporter.

When I was entering the details for the SQL Server I got an error that the password provided was incorrect. I reentered it and got the same error and then entered it a third time very slowly and carefully. Again, it was rejected.

Now because I was onsite and therefore using a customer supplied password there was every possibility that I had entered it incorrectly. I verified the password with the customer and then copied and pasted it in from Notepad so that I was certain it was correct, but it was, again, rejected.

It was at this point a memory fired that someone had recently told me about this. I checked emails I’d received a few weeks ago and found the answer in one from Andrew Cooper, my former colleague. The problem is when Enforce password policy in Microsoft SQL Server is enabled for the user account.

This should not be a problem, but with Management Reporter 2012 RU4 it is because the password is verified against SQL Server as each letter is typed in order to populate the database selection box and if the password policy is being enforced then the user account gets locked out after the third letter. I haven’t had a change/remembered to test this against RU5.

After unlocking the user account via SQL Server Management Studio, I copied and pasted the password into the Management Reporter Configuration window and was able to progress with the installation.

He somehow slipped it out without me noticing, but David Musgrave of the Developing for Dynamics GP blog released Support Debugging Tool Build 17 before Christmas; this is the build which added support for Microsoft Dynamics GP 2013.

He was back yesterday with a hotfix release to fix a couple of issues.

Partners can download SDT from PartnerSource (login required); if you’re a customer you’ll need to contact your partner to obtain it for you.

David has links to SDT for Microsoft Dynamics GP 10 and 2010 here.

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:

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.

[wpdm_file id=5]

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;

Continue reading “Microsoft Dynamics GP SmartList Default Visible To Company”

In the last couple of posts, I showed how to configure the server of Microsoft Dynamics GP by creating the System database and how to create a new company. In this post I’m going to run through deploying the Fabrikam, Inc. demo company.

To create the company, open GP Utilities (Windows Start menu » All Programs » Microsoft Dynamics » GP Utilities) by right clicking and select Run as Administrator. Log in as the SQL System Administrator (sa);

Continue reading “How To Deploy The Demo Company In Microsoft Dynamics GP 2010”

In the last post, I showed how to configure the server of Microsoft Dynamics GP by creating the System database. In this post I’m going to run through the company creation process.

To create the company, open GP Utilities (Windows Start menu » All Programs » Microsoft Dynamics » GP Utilities) by right clicking and select Run as Administrator. Log in as the SQL System Administrator (sa);

Continue reading “How To Create A Company In Microsoft Dynamics GP 2010”

In the last post I explained how to install the Microsoft Dynamics GP client and in this one I’m going to cover the server configuration. There is no server installation as such, as this can all be done from any client installation of Microsoft Dynamics GP.

To configure the Microsoft Dynamics GP server, right click on GP Utilities and choose Run as Administrator (Windows Start menu » All Programs » Microsoft Dynamics » GP 2010) and log in as the SQL System Administartor (sa);

Continue reading “How To Install Microsoft Dynamics GP 2010 – Server Configuration”