Hi Jason

I am still having problems with this. The issue is that the listsource
is potentially a large list of client codes (tens of thousands of
clients). Im not sure how the BDE handled this but we are actually
still using TIBOTables for a number of these (with Indexes to set the
ordering) but even this is not working. Do you have any ideas why this
might be?

Obviously this is not the best way to do searchs / data entry with IBO
what would people recommend as alternatives?

Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd



Jason Wharton wrote:

>How large is the dataset being selected from and what kind of network
>connection do you have to the server?
>
>You could try using TIBOTable and setup indexes to be ascending and
>descending and get a virtualized dataset that interacts with the server and
>only fetches records it needs, however it will always be fetching records
>from the server rather than scanning records in memory.
>
>Jason Wharton
>www.ibobjects.com
>
>
>
>
>>-----Original Message-----
>>From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
>>Behalf Of Robert martin
>>Sent: Thursday, July 07, 2005 9:08 PM
>>To: IBObjects@yahoogroups.com
>>Subject: [IBO] TDBlookupCombos
>>
>>
>>Hi all
>>
>>This might be a really stupid question but....
>>
>>We have come from a BDE / Dbase background and have used
>>DBLookupCombos
>>(in particular our customized descendant) to allow selection / Entry.
>>
>>We have a DbLookupCombo that lists product name and writes
>>its PK into
>>another table. I have set it to read from a TIBOQuery components and
>>all is well apart from when I try to locate a product beginning with
>>'Y'. It is not found. If I scroll to the bottom of the list it is
>>displayed and will then be found. I am assuming the
>>component is only
>>searching the data that has been buffered on the client side
>>and that by
>>moving to the end I force the component to 'pull' all the
>>data down from
>>the server. Indeed if I set 'AutoFetchAll' to true the
>>component works
>>fine. My assumption is that in the BDE version the component
>>searched
>>the buffer and if it failed, forced another block of data to be
>>downloaded until it found the record of ran out of data.
>>
>>Questions
>>
>>Do I have to set 'AutoFetchAll' or is there a better way of
>>doing it (I
>>don't want to pull the records unless I need to)?
>>Is there a better way of doing this? (we need to remain TDataset
>>compatible).
>>
>>TIA :)
>>
>>
>>--
>>Rob Martin
>>Software Engineer
>>
>>phone +64 03 377 0495
>>fax +64 03 377 0496
>>web www.chreos.com
>>
>>Wild Software Ltd
>>
>>
>
>
>
>___________________________________________________________________________
>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
>
>
>
>
>
>
>
>
>