Re: invalid class typecast
- From: "yc" <yc@xxxxx>
- Date: 25 Apr 2005 05:01:25 -0700
That's right to use Float is a soln. but not enough.
Because, int64 has a precision of 18 digit (may be closer)
on the other hand Float has less.
Seems like to me, the only soln. is not to use int64 only use
float instead
"Barak zabari" <lotemlotad@xxxxxxxxx> wrote:
>Parameters.ParamByName('REFNO').Value := li.Value;
>
>Useing D6 + ADO i run into lots of problems regarding the Value and
>LargeInt, if you will check the assignment you will probably see that the
>Value passed is wrong when the Value is larger then normal Int.
>In my case i gave up on BigInt and just use Float.
>
>
>"Mike Shkolnik" <mshkolnik2002@xxxxxxx> wrote in message
>news:426ccf08@xxxxxxxxxxxxxxxxxxxxxxxxx
>> > Why do you cast it as TLargeInt? This means the INT64 type while MS
>Access
>> > doesn't support INT64 fields.
>> MS Access database supports the INT64 fields. There is the dbBigInt field
>> type and this is same to ftLargeint in VCL
>>
>> --
>> With best regards, Mike Shkolnik
>> EMail: mshkolnik@xxxxxxxxxxxxx
>> http://www.scalabium.com
>>
>>
>
>
.
- References:
- invalid class typecast
- From: yc
- Re: invalid class typecast
- From: Andrew Ryazanov
- Re: invalid class typecast
- From: Mike Shkolnik
- Re: invalid class typecast
- From: Barak zabari
- invalid class typecast
- Prev by Date: Re: Insert, Update and Delete with Join Tables
- Next by Date: Re: invalid class typecast
- Previous by thread: Re: invalid class typecast
- Next by thread: Re: invalid class typecast
- Index(es):
Relevant Pages
|