size of ftInteger

When setting up parameters for a TAdoStoredProc:

CreateParameter('iCustID', ftInteger, pdInput, 10, iCurrCustID);

Generally you refer to numbers by their precision and scale where precision
is the total number of digits and scale is the number of decimal places.

But the What is the size? Is 10 correct?

According to the help on "CreateParameter":

"Size indicates the maximum size of the parameter's value."

I can't find anything that lets you set the scale or precision.

ALso, what if the is ftBCD? What is the size then if your actuall value is
something like 345.343?

Thanks,

Keith


.

Relevant Pages

  • Re: new here, my lang project... PT2
    ... The scale is limited by the resolution of ... I see this as a precision vs. accuracy issue. ... > physics core ... > just I am not sure how necessary the partitioning is at present. ...
    (comp.object)
  • Re: float storage
    ... To increase the scale one must decrease the precision. ... SQL> create table numberz, ...
    (comp.databases.oracle.misc)
  • Re: float storage and usage
    ... offers the maximum scale and precision.. ... float offers with widest ranges. ... Putting a float into a primary key is definitely not recommendable. ...
    (comp.databases.ms-sqlserver)
  • Re: float storage
    ... information scale and precision I can't determine in advance (customer data ... can vary wildly) so I wanted to use the datatype that offers the maximum scale ... I used the oracle 9i docs to drive my decision. ...
    (comp.databases.oracle.misc)
  • Re: rules of fixed-point arithmetic
    ... All fixed-point numbers have the same precision. ... keep your scale factors to powers of two, which is IMO not unreasonable, ... multiplications by arbitrary rational numbers. ... don't have to re-scale at all, except for when you reduce an accumulator ...
    (comp.arch)