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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pervasive SQL - ODBC Error: SQLSTATE = S1000, Native error code =

Status
Not open for further replies.

pempson

MIS
Oct 13, 2005
6
GB
Trying a simple insert statment, but for some reason it returns the following error no matter what i try and insert into the table:

ODBC Error: SQLSTATE = S1000, Native error code = -4977
The data buffer parameter is too short(Btrieve Error 22)

can anybody tell me what this error means and why i might be getting this error.
 
Typically that error is returned if your DDFs and data files don't match. WHat version of PSQL are you using? If it's V8.x, run a Database COnsistency Check from the PCC. If it's V9, download the Database CHecker from the Component Zone ( and run it.

Post any failures related to the table you are trying to insert into.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
using v8.5, where abouts would i find the consistency checker?
 
Right click the database name in the PCC, select "Tasks" then "CHeck database".

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
If the database fails the consistency checker with general dictionary inconsistencies on a particular table, then what?
 
all it tells me is that its failed, on general dictionary inconsistencies. Does the database need re-indexing?
 
===============================================
Database consistency test results.
Test was run on: 23 May 2006 14:47:47

DSN: TSNew

Database name: TSNEW

Database Location: D:\SHARE\APPS\TSPIRIT\DATA\RCI
===============================================


===============================================
Database Check Statistics
===============================================
Pervasive.SQL Compatibility Mode = 8
Tables Checked = 1
Tables Passed = 0
Tables Failed = 1

Illegal Object Names = 0
Record Length Inconsistencies = 0
Variable Length Column Inconsistencies = 0
Data Type Inconsistencies = 0
Column Overlaps = 0
Full Path (instead of Relative) Table Locations = 0
Table Files Don't Exist = 0
Index Inconsistencies = 0
System Table Inconsistencies = 0
General Dictionary Inconsistencies = 1


===============================================
===============================================
Problems Detected with Database Definitions
===============================================
+++++++++++++++++++++++++++++++++++++++++++++++
Table Name = PEEMAD

[Pervasive][ODBC Client Interface]Error in assignment.


===============================================
 
I've never seen that. Save the report (click the Diskette icon), and then post the entire report.


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Looks like we posted at the same time.

Sounds like your DDFs are really messed up. Are these for a third party application? If so, you should contact the vendor of the application to get updated ODBC compliant DDFs.
If not, I would suggest rebuilding the DDFs from scratch with the exact record structure.


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top