Subject | TDBlookupCombos |
---|---|
Author | Robert martin |
Post date | 2005-07-08T04:08:18Z |
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
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