Hi Tim,

> Does the customer use the DBISAM ODBC Driver
> to enter/modify data in this table ?

Nope. The previous version of my application (which used DBISAM) was written
entirely in Delphi 7. The current version of my app *was* using
ContextSoft's DBISAM ADO.NET provider to talk to a small Delphi 7 DBISAM
Server application, before upgrading to the ElevatedDB version.

Hedley


Was my bit of SQL any use?

Roy Lambert

Hedley,

<< Nope. The previous version of my application (which used DBISAM) was
written entirely in Delphi 7. The current version of my app *was* using
ContextSoft's DBISAM ADO.NET provider to talk to a small Delphi 7 DBISAM
Server application, before upgrading to the ElevatedDB version. >>

Okay, Bruno Krayenbuhl was kind enough to send me some code that may help
correct issues with BCD fields, but I have to test it with your source data
first.

I'll let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Roy,

>> Was my bit of SQL any use?

Sorry for the delayed response. I *think* your suggestion has worked! I've
tried it on a couple of databases i.e. I simply delete any records with the
amount > 0 and < 0.01 in DBISAM, and the migration to EDB then works
correctly.

My only concern is whether any of those records are actually valid, but I
can't see how they can be - especially as it's a currency field and the two
customers in question use £GBP which should always be to 2 decimal points.

Thanks for your input Roy - unless Tim can find a better solution, I'll
probably go with your suggestion and hope that those tiny amounts are all
invalid records.

Regards,

Hedley

Hedley


As you say its hard to see how they can be other than invalid. What puzzles me is how with a definition of BCD(2) did they ever get 3 decimals anyway. It was almost pure luck that I stumbled over it.

Anyway, even if Tim can't come up with something better at least you have something to use.

Roy Lambert [Team Elevate]

Roy,

<< Anyway, even if Tim can't come up with something better at least you have
something to use. >>

Bruno's fix worked great, so it will be in the migrators now to deal with
wonky BCD values.  Apparently the issue is that BDS 2006 and higher wasn't
coping with them some of the older BCD values properly due to the way that
they were originally created.

--
Tim Young
Elevate Software
www.elevatesoft.com