Data Access Worldwide Knowledge Base

Article ID 2052
Article Title ERROR: BTRIEVE: Invalid function dfbtrFileConvert Status: 21001
Article URL http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2052
KBase Category PERVASIVE.SQL
Date Created 10/19/2004
Last Edit Date 10/19/2004


Article Text
PROBLEM:
I am using Pervasive.SQL V8 and Visual DataFlex 10. If I try to convert databases to Pervasive from Database Builder I get the error
BTRIEVE: Invalid function dfbtrFileConvert Status: 21001

How can I correct that problem?

SOLUTION:
Subtract 21000 from the status code to get the PSQL error and this is the text of status 1 error from the PSQL help:

1: The operation parameter is invalid
The specified operation does not exist or is not valid.

You may receive this error if you are running a general-release version of the V8 client software against a pre-release version of the V8 database engine. If this is the case, you must uninstall your database engine and install the general release version.

If you have multiple paths specified in your DataPath (in the WS file), make sure you have the P.SQL server path first and then the regular Data path.
Example:
When the workspace DataPath is set to ".\Data;\\Sqlsvr\psqldata\TEST" the error happens. When the DataPath is set to "\\Sqlsvr\psqldata\TEST;.\Data" the error does not happen and the conversion succeeds.






Contributed By:
Sebok Zoltan


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.