[Pervasive][ODBC Client Interface]Error in assignment

[HTTP://PATELPLANET.COM]

-2147467259
[Pervasive][ODBC Client Interface]Error in assignment

I am using an ODBC connection to retrieve data ...and every now and
then I keep getting the above error message , the error is exactly
when you do a Recordset.movenext
Can any one help me...., I beleive this is the worst of ODBC drivers I
have ever seen.

http://patelplanet.com

[Bill Bach]

Sounds like a programming problem due to data types. See possible
solutions below...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
Bill...@goldstarsoftware.com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: November 12-15, 2002 - See our web site for details!

FYI: "[MS Excel][Pervasive][ODBC Interface]Error in Assignment" Error
Environment: Pervasive.SQL 2000, MS Excel 2000
Published: February 2001

Problem Description:
Exporting data from MS Query into an Excel spreadsheet returns the
following error message:
"[MS Excel][Pervasive][ODBC Interface]Error in Assignment"

Cause of this problem:
The problem happens when trying to return data from a MS query using ODBC
to an Excel spreadsheet. The SQLBindParameter is being called with a
cbColDef=510 (255*2). MS Excel 2000 is trying to bind the data to a
WVARCHAR thus the max storage needed in MS Excel application is 510 bytes
to hold 255 characters. ODBC specification requires that the driver
error out when this situation occurs. This problem only happens with Char
fields

Solution:
This issue will require a fix in the code from MicroSoft. We have
implemented a workaround to resolve this issue. The workaround will be
available in Pervasive.SQL 2000 Service Pack 3.

FYI: Error In Assignment" Occurs in SQLDM When SQL Statement Contains a
Text Value Not in Single Quotes
Environment: Pervasive.SQL 2000
Defect: 20875
Published: July 2001
Problem: "Error in Assignment" occurs in SQL Data Manager Query Builder
when SQL statement contains a text value not enclosed in single quotes.
Solution: Manually enclose text values in single quotes. The Query
Builder does not automatically enclose text values in quotes.
Example: CREATE TABLE class1(ID IDENTITY, "Name" CHAR(7), "Section"
CHAR(3))
INSERT INTO "Class1" ("ID", "Name", "Section") Values (0, 'MSB 202', 3)
The INSERT statements fails with "error in assignment" unless you enclose
the 3 in single quotes.

FTF: SQL function CONVERT returns error when trying to convert a string
into a real number if the decimal separator is set to ',' (Comma)
Environment: Pervasive.SQL 2000 WG Service Pack 2A
Defect: 32083
Problem description: SQL function CONVERT returns error when trying to
convert a string into a real number.
Example of statements returning error: SELECT CONVERT('1.23', SQL_REAL)
FROM Billing
ODBC Error: SQLSTATE = 22005, Native error code = 0 Error in assignment.
Expression evaluation error.
Since the locale setting for decimal separator was a "," either a "," or a
"." should be valid within the statement.
Cause of Problem: Locale German setting for decimal was set to ",". You
will not see this issue of the decimal separator is set to '.'
Solution: There is a FTF for this issue.