When you switch from one software vendor to another the chances are high that you need to export data cleansing and migration to the newly elected accounting program. SAP B1 is hosted in Microsoft SQL Server and import data is usually in the Data Transfer Workbench by filling CSV templates for each of the board.
In our opinion, the real challenge lies in the export of legacy accounting transactions, especially when they are hosted in the platform database Btrieve exclusive or even the organization of complex data. One of the most enigmatic legacy system in line with the ODBC connection and export accounting data is Great Plains for DOS, Windows or Macintosh, that was popular at the end of 1990. And still in production in versions 9.5, 9.2 and earlier. In this small publication we would like to discuss the data connection and export measures:
1. DDF files for the ODBC connection via MS Exchange or SQL command directly through invasive Center. We believe that the general control center is better than the ACP is sharing the same Btrieve file to accommodate more tables of parents requires data cleansing in SQL SELECT. As you may know that Pervasive Software is the successor to Btrieve. Btrieve DB and ODBC connection requires platform called "data definition files" or for short DDF: FILE.DDF, FIELD.DDF INDEX.DDF and when the latter is optional, but recommended as it improves the performance of the consultations. There are instructions in the manuals for ODBC available for review in the MPC installation CD. Instructions require that you have the original disks that were sent back to you later in the 1990th but customers often do not have more
