Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Btrieve Status 103 1

Status
Not open for further replies.

tvg212

Programmer
Oct 9, 2006
9
US
I am having this error (the chunk offset is too big) when using a LongVarChar field in my btrieve table. I created the table using the Create Table Wizard in Pervasive V8, and selected the advanced settings option. If the field is empty i am getting the error like when I try to access the table for the first time. Please help.
 
When dealing with Btrieve vs ODBC/SQL, a status 103 usually means that the DDFs don't match the data files.
Are you trying to create a DDF definition for an existing Btrieve file? If so, you should know that the LongVarChar/LongVarBinary and the LVAR/NOTE are different structures. THe LongVarChar/LongVarBinary are stored as an 8 byte integer in the fixed length portion of the record as a pointer to the end of the record. NOTE\LVAR fields are stored as the actual data at the end of the fixed length record (which is why you can have only one NOTE or LVAR in a table).

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
I am trying to create a DDF for a new Btrieve file. I am using Delphi 2006 to populate the data file, plus other 3rd party database aware components. I have one LongVarChar field and when i try to access the file for the first time (that field is empty) I am getting the Btrieve status 103 message. If I enter some data in that field, the error clears but recurs when i try to access another record that has no data in that field.
 
What interface are you using to access the Pervasive data (PDAC, BDE, Btrieve API, ODBC, ADO, etc)?
Do you get the error if you access the record using the Pervasive Control Center?


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Hi,
I am using Titan and Delphi 2006 to access my data, and no, I am not getting the error if I open the file in PCC.
 
Ahh.. That's the problem. I don't believe Titan has been updated to support the LongVarChar/LongVarBinary field. I believe it only supports the old Note/LVAR style fields which are considered legacy.

Have you tried PDAC (They are VCL components similar to Titan but support the LongVarChar/LongVarBinary.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Thanks,
A research on Titan shows Titan Version 10 for Delphi 2006 supports CLOB (type code 21). My thinking is that it would recognize my LongVarChar since its also type code 21. I have not tried PDAC but thanks for the info.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top