Great Plains on Pervasive SQL or Ctree redeployment overview

Great Plains on Pervasive SQL or Ctree redeployment overview
Current version 10.0 of Microsoft Dynamics GP, formerly known as Great Plains Dynamics is available on Microsoft SQL Server DB platform exclusively, and if you are currently enrolled in GP annual enhancement program, you are probably happy enjoying such Dynamics GP cool features as integration with MS Outlook, Sharepoint, SSRS, eConnect. For the rest of us, who are still on Pervasive SQL 2000/Btrieve or Ctree DB platforms (including Great Plains Dynamics on Mac Faircom), we would like to outline steps in redeploying Dynamics on new computer, it is especially helpful when you need to mount your new accounting application for the purposes of audit:
Great Plains Dynamics support options. Please, note, that Great Plains Software was acquired by Microsoft, however Microsoft Business Solutions retired Dynamics on non Microsoft SQL Server platforms in earlier 2005. This means, that you either should have internal IT resource, who is still familiar with Dynamics reinstallation and applying old service packs, or you should find Great Plains Dynamics Partner, who has consultants, familiar with old versions and their troubleshooting
Single user workstation install scenario. This method doesn’t require separate Pervasive SQL or Ctree server installation, and you can just use Great Plains Dynamics CD. Consider dedicating Windows XP workstation, Install Great Plains Dynamics in Single User Workstation mode, copy Dynamics folder from your old server and go to the next step - Location Translation procedure
Location Translation for Great Plains Dynamics. The reason for this step is simple - both Btrieve/Pervasive SQL and Ctree use Windows (or Mac OS) operating system file handling functionality (including user security to access, write and read DB files). Pathname tables store original Dynamics UNC path (or mapped drive), where Dynamics was installed originally, back to late 1990th, and since then, if you move Great Plains Dynamics to new server - you are doing original location (or original path) to new location/path translation. Typical location translation id is WINDOWS
Old Great Plains Dynamics on Pervasive or Ctree upgrade path. In your situation, upgrade path includes migration to Microsoft SQL Server 2000 step (this is usually done on version 7.5, you should consult your Great Plains Reseller on the steps to upgrade to Dynamics GP 7.5 on Pervasive or Ctree). When you are done with GP 7.5 migration to GP 7.5 on Microsoft SQL Server, you are on the open highway: popular route is 7.5->9.0->10.0