Question: When using the TpFIBDataSet, I do not seem to find a way to handle INT64 types. Help please.

Field "PROD_UNIT_PRICE" in Firebird = BigInt     =  2,200,000,000

Delphi
pFIBDSDetail=TpFIBDataSet

var
mfact:int64;
...
case pfibqreport.fieldbyname('TBL_Type').AsInteger of
4: mfact:=pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE').AsInteger

my result=
pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE').AsInteger comes through as -2094967296

There is not
pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE').asint64


How do I pass an Int64 through a TpFIBDataSet?


Answer:
Method "Fieldbyname" returns abstract class "TField". This class haven't methods for work with Int64 values.

pFIBDataSet has the psUseLargeIntField option in PrepareOptions. If
you include it into your code then FB Bigint field will do mapping
to TFIBLargeIntField. In this case you must write your code as:
4: mfact:=TFIBLargeIntField( pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE')).AsLargeInt

If you don't include psUseLargeIntField then this field will do mapping to TFIBBCDField.

In this case you should write your code as:
4: mfact:=TFIBBCDField( pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE')).AsInt64

And the last recommendation... If you can't know about prepareOptions in your code then you can write it as:
4:
  if pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE') is  TFIBBCDField then
    mfact:=TFIBBCDField( pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE')).AsInt64
  else
  mfact:=TFIBLargeIntField( pFIBDSDetail.fieldbyname('PROD_UNIT_PRICE')).AsLargeInt


Preview text: 
Prices in Euro:

235 (1 copy)
1250 (unlimited)

Volume discounts are available...

Navigation



We are a small software company with thousands of customers delivering comany wide systems including accounting, logistics, e-commerce, POS, sales etc etc. Several years ago, when we were still a very small company, we used Delphi 3 and Paradox combined with BDE. As our system (and customer base) grew I decided to switch to Delphi 5 and Interbase. Being a huge improvement over Delphi 3 and Paradox, I encountered numerous problems with IBX: memory leaks, performance issues and other problems. Borland was not to be bothered: IBX was provided "as is" and no support was avaliable. 
Not being very eager to use third party components with Delphi at first, I decided to give FIBPlus a try. At once all problems where gone: no more memory leaks and  performance was very consistent. 
But the real advantage of switching to FIBPlus came with the upgrade to D2005: after upgrading there were some problems with the new FIBPlus version. After emailing the problem I received an update within an hour! And this was at 11 pm! A few other (smaller) errors where handled in the same way. 
Our motto is: software is as good as its support. And support of Devrace is just great!
Just a little indication of our FIBPlus use: all our software runs 100% on FIBPlus. Our customers have a total of aprox. 4.800 Firebird databases in production, with a combined size of over 130TB and over 80 million transactions a day. Every
day. And FIBPlus has not failed a single transaction. Not once. There is, however, one (minor) drawback in using FIBPlus: while debugging an application which uses and invalid SQL instruction, de Delphi Debugger returns to the FIBPlus code instead of to our calling code (where the actual error comes from), thereby complicating de debug proces a little. But that is a very small price to pay for a otherwise brilliant third party solution! >>

Bas Jordans JorSoft Ltd
FOR CUSTOMERS
Download full versions and updates in your Personal Area