This status code can be returned in the following situations: The disk is full, and the file cannot be expanded to accommodate additional records. The application has attempted to perform an Update, Insert, or Delete operation on an RIï¿½controlled file that references another file. Also, in the Windows environment, be sure that the Btrieve for Windows DLLs and WBTR32.EXE are in your path or in the top level of your Windows directory. 21: The key The application is currently processing a wait transaction and tried to access a file that another user has locked. his comment is here
The workstation MicroKernel cannot assign a handle to the pre-image file because the MicroKernel was not started by a user with access rights to the pre-image file. There may two solutions: Btrieve File handle configuration may be set incorrectly in BTI.CFG. In this situation, Status Code 103 indicates that Btrieve made no changes to the record. 104: Btrieve does not recognize the locale. In this case, this status code is returned when Btrieve needs to add a page to the file, regardless of how much disk space is available. http://www.nomad.ee/btrieve/errors/88.shtml
If you have attempted an Insert operation on a file under referential integrity control, you may received this status code if a foreign key value in the record to be inserted Any of the following can cause this status code to occur: Clientï¿½based Btrieve has a file open, and another workstation that has the Requester loaded tries to open the same file. To reinitialize Btrieve, close all files, end/abort all transactions, and call WBTRVSTOP ( ) before calling the initialization function. 1017: Btrieve requester is unable to find the resource file WBTRVRES.DLL.
In the right hand frame, adjust the Create File Version. 050: The file owner is already set The application tried to perform a Set Owner operation on a file that already These two definitions are incompatible. The MicroKernel also returns this status code when it cannot create an index that does not allow duplicate key values because a duplicate key value already exists. 006: The key number If the disk is full, erase any unnecessary files. 16: The application encountered an expansion error.
Possible causes for receiving this status code are that the directory is full, the disk is full, or the disk is write protected. 34: The specified extension name is invalid. Conditions For Which Status Code 26 Is Returned The following conditions apply to the Btrieve Create API operation. For Windows 32-bit platform users: open a command prompt and run a DOS Btrieve application. Btrieve cannot enforce the Delete Cascade rule on a file under referential integrity control because the record that the application attempted to delete has more than 16 levels of descendants.
If you need to change the key numbers consecutive Get Next, Get Next Extended, Get Previous, or Get Previous Extended operations ( or in Delete or Update operations described in the Note Please see our Pervasive PSQL Knowledge Base for new and updated articles on Btrieve ActiveX Controls. Never use the same name for different ACSs, regardless of the version of Btrieve you are using. 05: The record has a key field containing a duplicate key value. Another related situation can also result in Btrieve returning this status code.
Your application tried to open a file in MicroKernel v5.x format using a v5.x MicroKernel; however, that same file was previously accessed by a v6.0 or later MicroKernel, which failed to http://support.elliott.com/knowledgebase/articles/834963-btrieve-error-codes-001-199 You attempted to create a file with the Replace option, and a bound MicroKernel data file with the same name and location already exists. Use the Clear Owner operation to remove the previous owner before specifying a new one. 51: The owner name is invalid. A key segment data type is BINARY ("Use Old Style Binary Data Type" flag is "on") and the segment length is odd. 030: The file specified is not a MicroKernel file
This additional byte causes the actual length of the index to be one byte longer, or 256 bytes. this content Btrieve returns this message only to Btrieve for windows applications that call WBTRCALL.DLL, or NLM applications that call Btrieve on the local server. 103: The chunk offset is too big. Preï¿½v6.0 versions of Btrieve return this status code when they encounter an error while writing the directory structure to disk prior to closing the file. You attempted to open a file with a long filename on NSS volumes.
To check for an owner name, use the NetWare utility NDIR. A delete action was attempted on a data file that is in continuous operations. Btrieve cannot open BTRIEVE.TRN. http://thesweepdoctor.com/the-application/the-application-has-encountered-an-error-and-cannot-continue.html The MicroKernel queries the volumes using OS calls and then loads the appropriate drivers for the associated name spaces it find for the volumes.
This error occurs through a SQL CREATE INDEX statement, or through the creation of a SQL PRIMARY KEY or FOREIGN KEY, if the index, or key, references a null CHAR column At the DOS prompt type net ver and press Enter. For example, a 200 byte key on a 512 byte page.
Here is info from the Status Codes doc.88: The application encountered an incompatible mode error The MicroKernel returns this status code in one of the following situations: If an application opens If you are a developer and you want more information about system transactions and this error, refer to the Btrieve for Windows Programmerï¿½s Manual. Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Pervasive: Btrieve Forum You will not encounter this error either in v6.x clientï¿½based Btrieve, or in serverï¿½based Btrieve. 48: The alternate collating sequence definition is invalid.
In the Btrieve for Windows environment, use the Save command from the Data menu of the Btrieve File Manager utility to retrieve the damaged fileï¿½s data records in a sequential file. Any file created with file version set to 7.x or later, and TRUENULLCREATE set to the default value of On, has true null support. Pre-v7.x files do not support these key types. check over here Also, make sure they are all on the same drive.
ActiveX control's buffers are not cleared and reallocated. Refer to Advanced Operations Guide for more information about RI and the Delete Cascade rule. 071: There is a violation of the RI definitions If you attempted an Insert operation on Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Close Box Join Tek-Tips Today!
For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO, both files will have preï¿½image files named CUSTOMER.PRE. Using the Btrieve Setup utility, specify a higher value for the Number of Handles configuration option. This status code applies only to Btrieve versions earlier than v6.0. 41: Btrieve does not allow the attempted operation. Pre-v6.x files do not support these key types.
In addition, consider status code 87: The handle table is full. You must retry the operation yourself; the MicroKernel does not automatically retry the operation. The MicroKernel returns this status code if you delete, move, or rename the extension files. 014: The MicroKernel cannot create or open the pre-image file The MicroKernel uses pre-image files only The keybuffer on the Btrieve create operation API (opcode 14) is set properly to create a file over an existing file.
The setting for the Number of Remote Sessions configuration option is too low. In Btrieve for Windows, the Btrieve DLL may return this status code if the task entry table is full. Check the RI constraints on your database. This status code often indicates a problem in nested transactions within your application. 038: The MicroKernel encountered a transaction control file I/O error This status code is obsolete in MicroKernel versions
You can receive this status code in the following situations: The Requester cannot establish a session with the server. This status code usually indicates one or more pages used to stored variableï¿½length records is corrupt. For the Version operation, the data buffer length is less than 5 bytes. 23: The position block parameter is not 128 bytes long. If the records' file is in v5.x format, this status code can indicate a file access conflict.
The Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operations use a buffer as work space. Smithware does not and cannot warrant the information, documentation, or software (including any fixes and updates) included in this distribution service or the performance or results obtained by using this information,