• Imports
  • About imports
  • Importing from Accounting Software
  • Importing from Working Paper Software
  • Importing from ProSystem fx Engagement
  • Importing from CaseWare Working Papers File
  • Importing from ASCII Text Files and Excel Files
  • Importing from Auditfile XML File
  • Imports and the SQL Server
  • Pervasive SQL
  • Comparison Report

Pervasive SQL

On some Windows operating systems, users with limited rights cannot import into Working Papers from any software that uses the Pervasive/Btrieve engine. To overcome this security constraint, you must modify the PVSW folder to give full permissions to the limited user before importing.

Changing user rights

1. While signed in using an administrator account on the machine, right-click the PVSW folder.
2. Choose the Security tab and give the limited user group Full Control of the PVSW folder.

The version used has to be compatible with the version that the import software package requires. To get the correct version of Pervasive needed, open the Database Service Manager.

Turning off local engine support

If you have a Pervasive/Btrieve server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, you must turn off local engine support.

1. Start the Pervasive PSQL Control Center. For more information, see the Starting PCC on Windows section in the Pervasive PSQL User's Guide.
2. Expand Local Client.
3. Right-click MicroKernel Router and select Properties.
4. If prompted, provide your login information.
5. Click Access.

6. In the right-hand pane, change the value:

   • Use Local MicroKernel Engine to Off.
   • Use Remote MicroKernel Engine to On.
7. Click OK.
8. Restart the Pervasive/Btrieve engine to use the new settings.