At 02:26 PM 11/09/2004 +0200, you wrote:

>hello Helen,
>
>I forgot to mention that I haven't still updated the ANAGRAPHICS SQL to use
>JOIN's instead of SELECT's, but I'll do ASAP.
>
>Here is the dfm code for TXProvQuery (PROVINCES), the lookup dataset
>(OwnProvQuery, the other query for the second combo is equal):
>
> object TXProvQuery: TIB_Query
> DatabaseName = 'WinContest'
> FieldsCharCase.Strings = (
> 'SHORT_NAME=UPPER')

OK!! - why do you need to enforce uppercase on this? If it is because you
are storing lowercase in one place and uppercase in another, then that
would explain why the incremental search misbehaves.

The keylink relationship won't work if there is uppercase on one side and
lowercase on the other. The FieldsCharCase is a display property, not a
data one.

> IB_Connection = MainDM.MainCN
> IB_Transaction = AnagTR
> SQL.Strings = (
> 'SELECT * FROM PROVINCES'
> 'WHERE ID_PROVINCE > 0'
> 'ORDER BY SHORT_NAME')
> ColorScheme = True
> KeyLinks.Strings = (
> 'ID_PROVINCE=ANAGRAPHICS.TX_PROVINCE')
> KeyDescLinks.Strings = (
> 'SHORT_NAME=TX_PROV')
> KeySource = AnagDS
> MasterSearchFlags = [msfOpenMasterOnOpen, msfSearchAppliesToMasterOnly]
> OrderingItemNo = 1
> OrderingItems.Strings = (
> 'SHORT_NAME=PROVINCES.SHORT_NAME;PROVINCES.SHORT_NAME DESC')
> OrderingLinks.Strings = (
> 'SHORT_NAME=ITEM=1')
> BufferSynchroFlags = []
> CommitAction = caRefreshKeys
> FetchWholeRows = True
> IncSearchKeyInt = 500
> Left = 320
> Top = 24
> end
>
>Maybe next you'll ask me the DDL for the two tables :-) Here they are:
>
>CREATE TABLE Provinces(
> ID_Province INT_SPECIAL_ID,
> Short_Name CH_PROVINCE_SHORT_NAME,
> Long_Name CH_PROVINCE_LONG_NAME,
> ID_Region INT_SPECIAL_ID,
> Award LOGICAL);
>
>CREATE TABLE Anagraphics(
> ID_Anagraphic INT_ID,
> Prefix INT_PREFIX,
> Unit INT_UNIT,
> Call_Sign CH_CALL_SIGN,
> Operator_Name CH_OP_NAME,
> City CH_CITY,
> TX_Province INT_ID,
> TX_Region INT_ID,
> Own_Province INT_ID,
> Own_Region INT_ID,
> Class CH_CLASS,
> Op_2_Prefix INT_PREFIX_CAN_BE_NULL,
> Op_2_Unit INT_UNIT_CAN_BE_NULL,
> Op_2_Call_Sign CH_CALL_SIGN_CAN_BE_NULL,
> Op_2_Name CH_OP_NAME_CAN_BE_NULL,
> Op_3_Prefix INT_PREFIX_CAN_BE_NULL,
> Op_3_Unit INT_UNIT_CAN_BE_NULL,
> Op_3_Call_Sign CH_CALL_SIGN_CAN_BE_NULL,
> Op_3_Name CH_OP_NAME_CAN_BE_NULL,
> Last_Progressive INT_ANAGRAPHIC_PROGRESSIVE,
> Can_Delete_Last LOGICAL,
> Certificates INT_CERTIFICATES,
> Amount NUM_AMOUNT);
>
>Regards
>Salvatore
>
>
>
>
>___________________________________________________________________________
>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
>
>
>
>