Great,Plains,Pervasive,SQL,Ctr computer Great Plains on Pervasive SQL or Ctree redeployment overview
Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc ----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a
For the rest of us, who are still on Pervasive SQL2000/Btrieve or Ctree DB platforms (including Great Plains Dynamics on MacFaircom), we would like to outline steps in redeploying Dynamics on newcomputer, it is especially helpful when you need to mount your new accountingapplication for the purposes of audit: 1. Great Plains Dynamics support options. Please, note, that Great Plains Software wasacquired by Microsoft, however Microsoft Business Solutions retired Dynamics onnon Microsoft SQL Server platforms in earlier 2005. This means, that you either should haveinternal IT resource, who is still familiar with Dynamics reinstallation andapplying old service packs, or you should find Great Plains Dynamics Partner,who has consultants, familiar with old versions and their troubleshooting 2. Single user workstation install scenario. This method doesnt require separatePervasive SQL or Ctree server installation, and you can just use Great PlainsDynamics CD. Consider dedicating WindowsXP workstation, Install Great Plains Dynamics in Single User Workstation mode, copyDynamics folder from your old server and go to the next step Location Translationprocedure 3. Location Translation for Great PlainsDynamics. The reason for this step issimple both Btrieve/Pervasive SQL and Ctree use Windows (or Mac OS) operatingsystem file handling functionality (including user security to access, writeand read DB files). Pathname tablesstore original Dynamics UNC path (or mapped drive), where Dynamics wasinstalled originally, back to late 1990th, and since then, if youmove Great Plains Dynamics to new server you are doing original location (ororiginal path) to new location/path translation. Typical location translation id is WINDOWS 4. Old Great Plains Dynamics on Pervasive or Ctreeupgrade path. In your situation, upgradepath includes migration to Microsoft SQL Server 2000 step (this is usually doneon version 7.5, you should consult your Great Plains Reseller on the steps toupgrade to Dynamics GP 7.5 on Pervasive or Ctree). When you are done with GP 7.5 migration to GP7.5 on Microsoft SQL Server, you are on the open highway: popular route is7.5->9.0->10.0
Great,Plains,Pervasive,SQL,Ctr