At 04:14 PM 10/10/2003 +0200, you wrote:

>I would suggest to provide more info in IBObjects help file at least in
>such topics as OrderingItems, OrderingLinks & SearchingLinks
>For the first time it's impossible to understand used format - only
>examples clarifies a little
>
>Such questions truely comes by reading at first time (I figured it for
>myself by reading group :)), so new readers need more information as it
>provided now. That's my suggestion
>
>OrderingItems:
>Entries should be made in the following format:
>< user readable name of sort >=< ascending ORDER BY criteria>[;< descending
>ORDER BY criteria >
> ^
>why user readable name of sort is needed at all? it never nowhere is used -
>maybe only for user convenience.

It is used by the Search bar - when the user clicks the Sort By (sbOrder)
button (leftmost button) the human-readable names are displayed as a pop-up
selection list.

>Short example would be great to (as Order
>by name=Name;Name DESC)

Have you explored the SearchingLinks sample app? Or the on-line FAQ?

>OrderingLinks:
>where is describted ITEM keyword - what it is used for? POS?

It doesn't have a description. ITEM and POS are keywords for two optional
elements in the OrderingLinks entry. If you include both, you need the
keywords; if you have just the item alone, you can omit the keyword
(though it's recommended to include it). ITEM is the OrderingLinks item,
POS is used to set the number of characters for refining (restricting) the
rows "windowed" in searching a large set.

>SearchingLinks:
>It should be defined in this format:
>[< tablename >.]< columnname >=< parametername >
> ^
>what do I need to write instead parametername? where it from comes? is it
>paramname from IB_Edit?

No, it is the parameter name for setting WHERE clause of the search. Say
you define an OrderingItem that is Surname. For a search on Surname, you
accept a string that is a surname or the initial characters of a
surname. If the OrderingLink has no POS included, the WHERE clause will be

WHERE aTable.Surname = :Surname

If a POS value is included, the WHERE clause would become

WHERE aTable.Surname STARTING WITH :Surname

Let's say you put 'McDonald' into your search field. Then, in non-POS
case, the actual SQL would be
WHERE aTable.Surname = 'McDonald'
whereas a POS=3 would cause the WHERE clause to be
WHERE aTable.Surname STARTING WITH 'McD'

--/ Gediminas /--

>The Truth Is Out There

very often it's so near to you that you fall over it

H.