I hope someone can give me a clue what is happening.
(read - I am begging for help)

Pervasive SQL 2000i SP4
ODBC connection Visual basic app.

Using the decimal data (decimal(21,3)) type when a zero is eneterd into a field pervasive saves an incorrect number and repeats this number in other fields of that record that are/were equal to 0 (zero).

Example:
field 1 = 0 (entered by user)
field 2 = 0
field 3 = 5.225
field 4 = 0

record updated

results:

field 1 = 2685403.136
field 2 = 2685403.136
field 3 = 5.225
field 4 = 2685403.136

If you use the PCC to enter 0 does it store the correct value? If so, then the problem is within the VB application. It's not a lot, but might help narrow down the problem.

Also, have you tried the SP4 HotFIxes? If those don't work, as a test you might try V8. Pervasive won't fix SP4 because it's in transition support.

thanks for the reply.
In PCC id does not seem to do this, however in stepping through VB the fileds show to be correct before and after the update.

I will look into the hotfixes.

Thanks again.

I applied the hot fixes and this did not seem to help the problem.

I discovered that if the first decimal field in the record contains a value not equal to zero (< or > zero) then the problem does not occur in that record.

Stepping through the VB code I am unable to locate the number that is written to the database.

Was able to find the problem with help.
There is an OLEDB FTF for this problem.

Pervasive.SQL OLE DB Provider version 7.94 SP4 FTF
Released 6/26/2003
Build 253.125

Bug Number Bug Description
------ -------------------------------------------------------
44790 Conversion problems with numeric and decimal datatypes

Good to hear you got it solved.

Do you have a link to this solution, i have the same problem...

unbelievable but i can't find it with the search function on the pervasive website :/

Thanks in advance.

You need to contact Pervasive to get FTFs. They don't post them because they don't get as much testing as a full service pack.

ok thanks for the tip!

I'll test pervasive 2000i sp4 first, i hope that fixes the problem aswell.

we're running 2000i SP3 at the moment...i know the problem is also fixed in V8, but we can't force all our customers to buy V8.