sql - List search results in a combobox -

I want to change our search because now it is a little bit that currently it works like this:

< Ol>

Enter a text in the user's text box, for example Volvo and start searching.

This search with SQL containing all posts containing Volvo

The result is a list with 2 columns, bolded and display values.

BoldID is a unique number to identify objects in the database

The display value that the user sees in the list of results.

Each line in the results list is identified with a line number in the users list 1 with the first, second with 2 and so on.

There is also a limit to show up to 99 hits by looping the query into the code. This is a query that returns many hits returns is not good because it does not mean that the list of users is high. In that case the search should be more specific.

The result list is displayed in a separate global window, which is called Daiyapa, that the part is that if you are searching with a model dialog, then DApplication should be uncompressed from the main window They can choose the value with the mouse. We suspect that this may be a reason that the application sometimes locks down with the modal dialogue behind the main window.

After the change, it should work like this:

Enter the text in the user, start searching on demand like the combo box and before SQL, but as a result it is displayed in Cambodia. So I probably want to change the display, because there are very old SQL queries that are in use and now works fine.

We use components of the Delphi 2007, Interbase 200 and Dev Express. Yesterday I tried to connect a custombox to the combobox, but I know that it has not yet been implemented. See . I want to use a custom data source to apply the row number and apply the maximum number of hits. C 6 and 7 in the list given above.

So now I see 2 options:

• Use a DB-awake combobox
• Use a textbox and display the result Attach a grid to it.

The Combobox is simple because it is a complete component, but I do not know how to implement feature 6 and 7 from the above list, Textbox + grids give more freedom but more work is required. is.

I like the first option. The current problems are:

• I think the interbase can not restrict the amount of hits in SQL results This code should be done with how it is done with DB-aware combobox?
• How can I show line numbers in the number of results?
Update 1: Thanks for the necessity 7 Thanks, for thanks, as 6 I think it's hard. Ideally I want it in SQL so that I can remove it like my column. But Interbase does not support it.

requirement 6:

assuming that ID value of DB is an integer , You can use the tag of a control or string object in the consonance / list box to store the ID value.

[Pseudo Code]

  do not have a combo box, while not. ITEM Add object (& lt; display text db>, integer id with tubact (& lt; db & gt;));  

and use this

  id: = integer (combo box. Items. [Combo box. Itam index]];  

Requirement 7:

Using the Dob Walked Combobox / Listbox via query is eof or outside of 99 rows. So you will need to rely on SQL even if you do not want to change any of the existing SQL statements, you can use the "top" feature of SQL to limit the number of rows. . For example,

  SELECT TOP 99 FROM (& lt; your native SQL & gt;)  

You can use the phrase in the Interbase SQL :

ROWS 1 to 99

Just after the order section (see example - Approximate page Below)