Btrieve

- The application should rerun if it receives a status code 84.

- Btrieve will lock the key page for some time

- At this moment another user may try using it.

- Verify the number of file servers, the /s parameter on Brequest whether it large enough

- If the number is higher, it may stop the status 38.

- Check the /s parameter (number of file servers) on Brequest to see if it is large enough. A higher setting may stop the status 38.

C long integer can be defined as a key in Btrieve by specifying the key as an integer. But the length need to be specified as four bytes.

Btrieve is a transactional database, navigational database software product. It is based on Indexed Sequential Access Method (ISAM), which is a way of storing data for fast retrieval. There have been several versions of the product for DOS, Linux, older versions of Microsoft Windows, Windows 98, Windows NT, Windows 2000, Windows XP, Windows Server 2003, 32-bit IBM OS/2 and for Novell NetWare.

The following are the factors

- The page sizes of Btrieve are set to 1024 and 512 bytes

- All the workstations are configured with IPX v2.15

- The disk block size was set to a size apart from default 4k block size

- These factors cause a minor Btrieve performance degradation.

The following are the combination of factors to improve performance.

- Rebuild the file size of Btrieve with a page size of 4096 bytes

- Upgrade IPX to v3.10

- Recreate all the volumes block size with 4k

- The 62 Status is an error in the descriptor / extractor.

- The first two bytes of the data buffer need to contain the exact length of the data buffer that are sent to Get Next Extend operation

- The Data Buffer length need not be the4 exact length

- If any other variable is defined, the data buffer would be overwritten

The reasons for this are

- An alternate collating sequence might be used

- This require to allocate an additional 265 bytes in the data buffer

- Nine bytes are allocated for the name of the collating sequence and 256 bytes are allocated for actual sequence

-"Total" column gives the number of UNIQUE values for every key

-The column is different from "Total Records" column

The following engines are required to run Btrieve on SFT III server.

- Btrieve.nlm on MSEngine

- BSPXCOM.NLM on MSEngine

- AFTER311.NLM on IOEngine

- Btrieve is unaware of running SFT III Server

- The I/O and mirroring will be taken care by OS

-DDF editor allows to create the description of files

-DDF is necessary to access Btrieve files through ODBC / OLE

- Allows to

-create / view / edit dictionary DDF

-import and export data from ODBC data source

-drag and drop / copy and paste the descriptions

-rebuild files

-search filtration data

-Yes. First the DOS requester is loaded

-Later windows is loaded

-While the windows application is running,

- The first window calls Btrieve to load and Btrieve Request Interface for windows.

-INVALID OPERATION – The parameter of the operations of a call is invalid

-I/O ERROR – An error occurred during a disk read / write operation.

-FILE NOT OPEN – Any operation on the designated file can not be performed as the file is not open

-KEY VALUE NOT FOUND - The designated key value is not found in the index path

-INVALID POSITIONING - Each time the current position need to be established. This position is application for update / deletion of a record.

- Btrieve is a navigational database product

- Based on Indexed Sequential Access Method(ISAM)

- ISAM is a way of fast data retrieval

- Btrieve retrieves one record at a time.

- Transaction Operation is faster as there is little overhead with Btrieve Engine

-Data available in a file can be shared by using Single Engine File Sharing and Multiple Engine File Sharing modes.

-SEFS is allowed only to the clients to access the engine for altering databases.

-MEFS allows multiple clients running under multiple engines for accessing the database.

NetWare Btrieve v6.x can access both v5.x and v6.x format files simultaneously and the performance is proper.

When you attempt to open v56.x file with v5.x version, a status (I/O error) will be returned

-System transactions are non-transactional operations

-System transactions are used for data recovery using MKDE.

-User transactions are concurrent transactions.

-User transaction might have lost when a recent transaction was rolled back

-When a user transaction is rolled back, an option might be set which causes the MKDE to force the system transactions.

- No. Because Btrieve always bypasses the bit 7 of the key flags at the time of creation.

- The bit 7 is designated as an index supplemental

- The indexes are created as permanent.

- Yes. the right creation is necessary.

- Btrieve may create a file called pre-image file, in accelerated mode.

- During an insert(2), an index does not allow the duplicates and the insertion of records causes a duplicate error that is to be returned.

- Any pages that have been updated already for the insertion, would need to roll back.