Clients who have upgraded to Microsoft Dynamics GP 2010 can use the new remember user and password functionality, but what about those who have not yet upgraded?

Well, in Microsoft Dynamics GP 10, and before, you can use a login macro to automate the login process. A macro can be created by pressing Alt + F8 on the login screen and following the normal login process before pressing Alt + F8 again to stop recording. Continue reading “Automate Login To Microsoft Dynamics GP 10”

I have recently been upgrading an existing client to Microsoft Dynamics GP 2010 R2 from GP 10 SP1 on their test system. As they have lagged somewhat on versions I needed to upgrade them to GP 10 SP5 before then upgrading them to GP 2010 R2.

They recommend that packages should be moved around using the Customisation Maintenance (Microsoft Dynamics GP menu » Tools » Customise » Customisation Maintenance) to Import/Export the modified reports. Rather than doing this, which runs the potential risk of leaving client machines with an outdated REPORTS.dic we have been pointing the clients at a centralised REPORTS.dic on a server and copying only the Dynamics.vba to each client (we change the reports more often than the VBA).

Using Customisation Maintenance to Import the package file to each client would have prevented the problem as it would use the Microsoft ActiveX Data Objects 2.7 Library reference on the local machine. Doing it the way we do, by copying the VBA, transfers the reference within the VBA file.

This is an issue for internal discussion and we perhaps need to change the process we use for dictionary files.

I implemented the VBA workaround for cheque remittances on a test system for another client site, to make sure they don’t see the undefined symbol error, the other day after I upgraded Microsoft Dynamics GP 10 to GP 2010 and tested the remittance to ensure it worked. amend VBA on Server 2008 R2 SP1

When the client came to test the remittance themselves on the test Citrix Server they got a type mismatch error;

I like dealing with Microsoft Dynamics GP as it is easy to use and is a very flexible system. I don;t enjoy using some of the related systems as much and most especially Integration Manager.

We have a few customers who use it for importing journals or invoices into the system from elsewhere and occasionally they encounter errors which are more than an incorrectly formatted file so they contact the helpdesk to log a call.

One of the issues which has annoyed me about Windows 7 for a while now has, since I started writing this blog, moved on from being an annoyance to being seriously aggravating. It’s a meme I don’t really like but it does perfectly convey my emotions;

The recent test upgrade for a client I did between Microsoft Dynamics GP 10 SP5 and Microsoft Dynamics GP 2010 R2 hit a minor snag during the GP Utilities section of the upgrade which resulted in this error message;

Over the last two or three years the VAT rate in the UK has changed three times; temporarily down to 15% from 17.5% and then back up a year later before a permanent rise in January 2011. On each occasion we issued advice to customers on how to handle these changes within Microsoft Dynamics GP; there were two ways for them to make the change; either create a new Tax Detail or amend the existing one. Personally I recommended the former as it is somewhat cleaner; you can tell at a glance what the VAT rate will be without the need to check the date the invocie was registered. If the latter option was taken users needed to remember which rate is effective on what date during the cross over period which means lots of scope for errors. Continue reading “Feature Explained: Date Effective Tax Rates”

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

Click accept to confirm you agree to the use of cookies (failure/refusal to do so may render the site inoperable). more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.