Imports and The SQL Server
When you want to import data from certain accounting software applications, but do not have the accounting software installed or have access to its database, you must have a local SQL Server instance installed on the computer you are using for the import.
How it works
At minimum, the version of SQL Server used to import engagement data should be the same version as the one used to create the import files. Generally, we recommend that the latest version of SQL Server be used, although each application has unique requirements for importing in addition to needing a version of SQL Server.
The following applications require a local SQL Server instance be installed on the machine performing the import:
- Access Accounting Dimensions
- Big Red Book
- Microsoft Dynamics GP
- IRIS Accounts Production
- Microsoft Dynamics C5 Inventio - MSSQL
- Microsoft Office Accounting
- Microsoft Small Business Accounting
- Palladium Accounting
- ProSystem fx Engagement and ePaceENGAGEMENT 3.0
- Ufsoft version 8.2/8.5
SQL Server Versions
To facilitate the import of engagement data from the list of accounting programs above, you must have a local SQL Server instance installed on your machine. The following SQL Server instances can be installed:
| Version | Notes |
|---|---|
| SQL Server 2012 | Backward Compatibility Components are required. Install SQLServer2005_BC.msi from Microsoft SQL Server 2008 Service Pack 2 Feature Pack here. |
| SQL Server 2008 R2 | |
| SQL Server 2008/Express Edition | |
| SQL Server 2005/Express Edition | If you are running a Windows Vista OS, be sure that the system requirements are met. |
| SQL Server 2000/Desktop Engine Service Pack 4 (MSDE) | This is the free, redistributable version of SQL Server 2000 with the latest Service Pack. If you are running a Windows Vista OS, you will not be able to install this version |
Note: With the above SQL Server instances, ensure that you can log on as a system administrator and that the convert data path and all data files are in a local path.
For the latest version of the Microsoft SQL Server, visit the Microsoft Download Center and follow the download instructions.
Notes
- For a list of all installed SQL Server or MSDE instances on your computer, go to Control Panel | Add or Remove Programs.
-
Any existing SQL Server or MSDE instance can be used by import as long as you know the Administrator Login ID and Password to that instance.
Note: We do not recommend using SQL Server or MSDE instance installed by other software packages. You should install either a default or a new named instance that will be used only by import.
- In the Server box, type in the full qualified name of a running SQL Server or MSDE instance, which is in the form of, YourComputerName\SQLInstanceName. For example, Jason\SQL2000 (case insensitive)
- If you are using the default (nameless) SQL Server or MSDE instance, simply leave the Server box blank (you may need to read Microsoft documentation to learn how to set up a default instance).
-
Do not use the SQL Server or MSDE instance installed ProSystem fx Engagement (default instance name PROFXENGAGEMENT) when the import is taking place on the machine where ProSystem fx Engagement is installed. There is a conflict between the CaseWare import and ProSystem that import can overwrite internal ProSystem databases without any warning. If this happens, ProSystem fx Engagement will no longer work once the import is complete.
For more information, contact CaseWare Support for the latest version of the ProSystem fx Engagement Conversion Guide for Working Papers and Connector.
