Installing Microsoft Dynamics GP 2010 – Insufficient Privileges To Modify The VBA Project Error

Microsoft Dynamics GPI upgraded a clients test system from Microsoft Dynamics GP 10 SP3 to 2010 R2 successfully on the main system such as installing the main client and upgrading the system and company databases.

The client has a few modified reports on the system which needed to be brought across to Microsoft Dynamics GP 2010. These reports were exported from Customisation Maintenance (Microsoft Dynamics GP menu » Tools » Customise » Customisation Maintenance);

Customisation Maintenance

Continue reading “Installing Microsoft Dynamics GP 2010 – Insufficient Privileges To Modify The VBA Project Error”

Check Remittance Run-time error ’13’ – Type Mismatch: Follow Up

Microsoft Dynamics GPWe 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.

Check Remittance Run-time error ’13’ – Type Mismatch

Microsoft Dynamics GPI 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;

Run-time error 13: Type mismatch

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

Check Remittance Vendor Address VBA Workaround

Microsoft Dynamics GPFollowing on from yesterdays post about the Undefined Symbol error, where I discovered that Microsoft have removed the link from the check remittance tables to PM Creditor Master, I thought it might be useful to post the VBA workaround used to get the creditor address.

The first step was to create five Calculated Fields on the Check Remittance report; for simplicity I named them CreditorAddress1 through CreditorAddress5. No separate field for Post (Zip) Code was created as addresses can be of all different lengths and I like to output tidy addresses where I can.

Once the fields were created and added to the report, in the Remittance Header section, they were selected and made available to Visual Basic. Continue reading “Check Remittance Vendor Address VBA Workaround”

Check Remittance Undefined Symbol Error When Upgrading to Microsoft Dynamics GP 2010

Microsoft Dynamics GPThe customer I recently upgraded from Microsoft Dynamics GP 10 to GP 2010 have encountered an error during the payment run at the cheque remittances step;

Undefined Symbol F01343D00789 Sequence Num

Continue reading “Check Remittance Undefined Symbol Error When Upgrading to Microsoft Dynamics GP 2010”