Great Plains Location Translation Error Message Notes

Microsoft acquired Great Plains Software on the edge of the centuries and since then Microsoft formed Microsoft Business Solutions subdivision to deal with GP, AX, SL, RMS, CRM.  MBS abandoned Pervasive SQL and Ctree DB platforms beginning with Dynamics GP (new name for Great Plains Dynamics ERP, MRP, and accounting application).  Well, let’s go back to the topic and concentrate on Great Plains move to new server, UNC path and automatically triggering Location Translation dilemma.

1.       Btrieve and Ctree data handling.  These budget DB platforms do not require Client-Server optimization and Pervasive/Btrieve handles DB access on Windows Operating System level to give you the idea.  It is also applicable to Great Plains Accounting for DOS and Windows: 9.5.t is also applicable to Great Plains Accounting for DOS and Windows: 9.5, 9.2, 9.1 or older versions (GPA was available on Btrieve and Macintosh)

2.       Great Plains Dynamics Location concept.  Great Plains Dynamics on Ctree, Btrieve or its improved version Pervasive SQL 2000 handles DB files through OS system, meaning Windows XP or Vista file handling.  The path of the Dynamics database is stored in Location table, and this is understandable

3.       Location translation procedure.  You could try it in-house, however it is recommended to outsource to Great Plains Technical Consultant.   Please click on Great Plains Utilities window See Existing Locations option, write down the path, then change location to what it is now – you can use UNC Path, mapped drive (such as E:, F:, etc.)

4.       Legacy Great Plains version data repair.  We recommend you to use Microsoft Access and its Linked Tables approach to hook up Pervasive or Ctree data tables, then you should be able to edit GP data fields, be cautious, however, we recommend you to review Great Plains tables structure: Tools->Resource Description->Tables