Subject | Re: [IBO] Where did the asInt64 go? |
---|---|
Author | rjbelland |
Post date | 2005-12-14T05:35:40Z |
Hi,
Odd indeed....
But if I am do something like...
IBOQuery.Params[i].asString := ParamList[i].AsLargeInt
then the compiler complains of incompatible types.
-Rene
Odd indeed....
But if I am do something like...
IBOQuery.Params[i].asString := ParamList[i].AsLargeInt
then the compiler complains of incompatible types.
-Rene
--- In IBObjects@yahoogroups.com, Hans <hhoogstraat@s...> wrote:
>
> a safe way, oddly enough. AsString
>
>
> ----- Original Message -----
> From: "rjbelland" <rbelland@u...>
> To: <IBObjects@yahoogroups.com>
> Sent: Tuesday, December 13, 2005 10:06 PM
> Subject: [IBO] Where did the asInt64 go?
>
>
> Hello,
> I upgraded to ver 4.5 from ver 4.2.
>
> In ver4.2 I could use the following:
> IBOQuery.params[i].asInt64
>
> I cannot do so in ver4.5. I have to do:
> IBOQuery.params[i].asInteger or IBOQuery.params[i].value
> I get and "undeclared identifier" error when compiling
>
> What has changed? Which should I be using? asInteger or .value?
>
> Thanks,
> René
>
>
>
>
>
>
>
___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
> without the need for BDE, ODBC or any other layer.
>
___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>