From the Microsoft Dynamics GP Blogs: Logical File Names; Upgrade Errors; Canadian Tax Calcs; No PO Ship To Auto Fill

A selection of the latest insights from the Dynamics GP blogs:

• Changing the Logical File Names Of A SQL Database;
• Error Messages When Upgrading to Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015;
• How YTD CPP & EI Factor into Tax Calcs;
• Purchase Order Ship to Address Assignment or Why won't Purchase Order Ship to Address Auto Fill?

Changing the Logical File Names Of A SQL Database

On his AzureCurve blog, Ian Grieve noted that when a database is created, a logical name that matches the physical name is assigned to it.

But when you're working with Microsoft Dynamics GP, you often create a live database as well as a test database. Then you populate the settings in the live database and replicate over the top of the test one. He continues:

"Or on occasion we have created a template database which then gets copied when a new company is created (this method is often used for clients who have a substantial amount of setup in third party modules which the PSTL Company Copy doesn't cater for).

The problem with both of these is that when a database is restored elsewhere it brings it’s logical name with it; meaning a mismatch between the logical and physical names which causes problems when backing up and restoring databases.

But all is not lost, he added. You can find out how to handle issues related to mismatched logical names this problem here.