We heard back from the Development Team in Fargo, who David Musgrave contacted regarding the issue we encountered with the Microsoft ActiveX Data Objects 2.7 Library.

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;

Continue reading “Check Remittance Run-time error ’13’ – Type Mismatch”

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”