Subject | Re: [IBO] IB_LookupCombo questions |
---|---|
Author | Helen Borrie |
Post date | 2005-11-10T23:12:57Z |
At 01:03 AM 9/11/2005 +0000, you wrote:
This is NOT how the tib_lookupcombo is designed to work. Its purpose is to
link one record in the lookup dataset to one or more records in a database
table. In short, it is never going to work with your structures.
1. The Keysource set is a join between a table (that has a 5-segment
primary key for no obvious reason) and a stored procedure that takes inputs
from the user.
2. The lookup set is the stored procedure itself, parameterised with the
same inputs as the Keysource set.
This is all wrong for a tib_lookup combo. You shouldn't have a
parameterised set in this control, anyway; and certainly not one that is a
SP whose input parameters depend on the current record in the
keysource. The SP for the lookup set will have to run in its entirety
each time you scroll the Keysource set!
You might be able to get something working by using a TIB_ComboBox. But,
really, if I were you, I would want to take a hard look at my database
structures. Relational databases are about relations between tables, not
about coincidental relationships between derived outputs. If you can't make
these relationships meaningful *in the database* then there's something
seriously wrong with the design.
Please don't ask me to help you to make this work the way it is now. It won't.
Helen
>Hi, I'm using Delphi 7, Firebird 1.5 and IBO 4_5_B.Because that's the only time when this relationship is valid.
>I have been trying for many days to solution this problem, but I
>couldn't yet.
>Would somebody, please, help me why IB_LookupCombo:
>1) Only shows text when cursor is on the control
>2) Can't type anything on control, only allows select on dropdown listThe Keysource dataset is not updatable.
>3) Dropdown list width is inappropriate, because first column is tooYou fixed this, right?
>large
>I put a very small sample with DB, please unzip it on a fold C:\RFSample
This is NOT how the tib_lookupcombo is designed to work. Its purpose is to
link one record in the lookup dataset to one or more records in a database
table. In short, it is never going to work with your structures.
1. The Keysource set is a join between a table (that has a 5-segment
primary key for no obvious reason) and a stored procedure that takes inputs
from the user.
2. The lookup set is the stored procedure itself, parameterised with the
same inputs as the Keysource set.
This is all wrong for a tib_lookup combo. You shouldn't have a
parameterised set in this control, anyway; and certainly not one that is a
SP whose input parameters depend on the current record in the
keysource. The SP for the lookup set will have to run in its entirety
each time you scroll the Keysource set!
You might be able to get something working by using a TIB_ComboBox. But,
really, if I were you, I would want to take a hard look at my database
structures. Relational databases are about relations between tables, not
about coincidental relationships between derived outputs. If you can't make
these relationships meaningful *in the database* then there's something
seriously wrong with the design.
Please don't ask me to help you to make this work the way it is now. It won't.
Helen