Subject | Re: IBO 4.9.14 Build 11 released. |
---|---|
Author | patrick_marten |
Post date | 2011-09-02T08:52:43Z |
--- In IBObjects@yahoogroups.com, "Support List" <supportlist@...> wrote:
how / where can the option lopCheckOnServer be set? I have a strange behaviour using Locate and would like to check, if that's due to this change or not.
As far as I can see, IBOTable, IBOQuery etc. still use TLocateOptions and not TIB_LocateOption...
Regards,
Patrick
>Hello,
> I've fixed a couple issues and released a new version.
>
> This release should resolve Thomas's issue calls to Locate() generating a
> fetch from the server looking for a record that it couldn't find. Thomas
> wanted the Locate() method to not bother checking on the server if all of
> the records were already fetched into the client buffers. I decided this
> would be a good thing and made it default to not check the server but if you
> still want the old behavior you can add the lopCheckOnServer option in the
> call to Locate() if you want it to make sure.
>
> I also fixed the problem having to do with the byte length of string columns
> being reported instead of the character length in the TIBODataset based
> datasets.
>
> Regards,
> Jason LeRoy Wharton
> www.ibobjects.com
>
how / where can the option lopCheckOnServer be set? I have a strange behaviour using Locate and would like to check, if that's due to this change or not.
As far as I can see, IBOTable, IBOQuery etc. still use TLocateOptions and not TIB_LocateOption...
Regards,
Patrick