Btrieve API Improvements
Distributed Tuning Interface Improvements

Increased Accuracy in Extended Percentage Operations
Delete and Rename Subfunctions for the Create Operation

Revisions to the percentage operations implementation that improve the accuracy of the operations.
The addition of a granularity setting in both operations that allow you to choose the factor by which the percentage is measured. In previous releases, this value was always 10,000.

---

Note
The improved accuracy in Pervasive.SQL 9 is available whether or not you use the expanded API to specify a granularity other than 10,000.

---

Place ExPc in the second four bytes of the data buffer.
Place the desired granularity in the third four bytes as a LoHi Intel integer. The granularity you choose can be any number from 1 to 0xFFFFFFFF.
Ensure that your data buffer length is at least 12 bytes.

The previous functionality of the Create operation is intact. Follow the existing documentation on the Create operation if you want to create a new MicroKernel data file.
The RenameFile and DeleteFile subfunctions cannot be used on files that are bound to specific databases because they do not affect the contents of the miscellaneous page.
If a file contains an Owner name, the owner name check is not performed by the new subfunctions. The owner name is still needed to view the contents of the files.

New APIs to better integrate with the security features introduced with Pervasive.SQL v8.5.

For more information, see:

PvOpenDatabase()
PvCloseDatabase() .
PvSecureDatabase()
PvUnSecureDatabase()
PvIsDatabaseSecured()

As part of this addition, the PvCreateDictionary() and PvOpenDictionary() APIs are now deprecated. Future releases will not support these APIs although support is not removed for them in Pervasive.SQL 9.

New PvCopyDatabase() API to copy an entire database to a new database, adjusting referential integrity if needed.

For more information, see PvCopyDatabase() .

Expanded return codes for PvConnectServer() so that you can better detect the exact cause of a connection failure.

For more information, see Enhanced PvConnectServer() Error Messages .

PvDropDatabase - a previously reserved parameter is now used as an options bitmask. Substitute the following table row for the options parameter for PvDropDatabase() in the Pervasive.SQL v8.5 SDK documentation.

In

option

Bit mask that specifies options. Set the low order bit to one (0001h) if you want data files to be deleted in addition to the database name. Otherwise, only the database name will be deleted but data and DDF files will remain.

The following restrictions have been added to PvAddTable().
If you use PvOpenDictionary() to obtain a dictionary handle, you will encounter an error (PCM_errFailed) if you use PvAddTable() against a secured database. Use PvOpenDatabase() instead and specify security credentials.
When describing the indexes, you must ensure that every index has segment numbers beginning with zero. When the index contain multiple segments, each segment must start numbering at zero. If no zero is found, you will encounter the error PCM_errFirstSegmentNumberMustBeZero.

BTI_API PvOpenDatabase( 
	BTI_LONG           hConnection, 
	BTI_CHAR_PTR       dbName, 
	BTI_CHAR_PTR       dbUser, 
	BTI_CHAR_PTR       dbPassword, 
	BTI_WORD_PTR       dbHandle); 

DTI session started by calling PvStart()
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.
If the database has security enabled, you must specify a valid database user name and password. Security for the returned database handle is enforced based on the access rights defined for the database, and should match behavior seen in SQL or ODBC interfaces.

PRESULT PvCloseDatabase( 
	PS_UINT16       dbHandle); 

DTI session started by calling PvStart()
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.
Valid database handle returned by PvOpenDatabase() .

BTI_API PvSecureDatabase( 
	BTI_LONG           hConnection, 
	BTI_CHAR_PTR       dbName, 
	BTI_CHAR_PTR       dbUser, 
	BTI_CHAR_PTR       dbPassword); 

DTI session started by calling PvStart()
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.
When you enable database security, you must specify Master as the database user name and choose a password. Security for the database is enforced based on the access rights defined for the database, and should match behavior seen in SQL or ODBC interfaces.

BTI_API PvUnSecureDatabase( 
	BTI_LONG           hConnection, 
	BTI_CHAR_PTR       dbName, 
	BTI_CHAR_PTR       dbUser, 
	BTI_CHAR_PTR       dbPassword); 

DTI session started by calling PvStart().
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.
Database is secured

BTI_API PvIsDatabaseSecured( 
	BTI_LONG           hConnection, 
	BTI_CHAR_PTR       dbName, 
	BTI_LONG_PTR       secured); 

DTI session started by calling PvStart()
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.

BTI_API PvCopyDatabase( 
	BTI_LONG           hConnection, 
	BTI_CHAR_PTR       dbName, 
	BTI_CHAR_PTR       newdbName, 
	BTI_CHAR_PTR       newdictPath, 
	BTI_CHAR_PTR       newdataPath); 

DTI session started by calling PvStart().
Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.

BTI_LONG connectionHandle = P_LOCAL_DB_CONNECTION; 
BTI_CHAR_PTR newdataPath = "c:\\data\\gallery2"; 
BTI_CHAR_PTR newdictPath = "c:\\data\\gallery2"; 
BTI_CHAR_PTR databaseName = "Gallery"; 
BTI_CHAR_PTR newdatabaseName = "GalleryCopy"; 
BTI_SINT status = 0; 
BTI_CHAR_PTR server = "MyServer"; 
BTI_CHAR_PTR user = "Administrator"; 
BTI_CHAR_PTR pwd = "Admin"; 
//only need to connect to server if it is remote 
//otherwise can pass P_LOCAL_DB_CONNECTION for the 
handle 
status = PvCopyDatabase( 
connectionHandle, 
databaseName, 
newdatabaseName 
dictPath, 
dataPath);