/**************************************************************
*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*
*************************************************************/
#ifndef __com_sun_star_form_component_DatabaseListBox_idl__
#define __com_sun_star_form_component_DatabaseListBox_idl__
#ifndef __com_sun_star_form_component_ListBox_idl__
#include The base service for list boxes ( This service here extends this mimic. It allows to fill the list from a data source.
This means that a second result set is opened, which works on the same connection as the
form which the list box belongs to, but can be based on an arbitrary table or SQL statement. For instance, you may have a form which is bound to a table invoice, and you use it
to enter invoices for your customers. Probably, you will have a second table (say customer),
which (amonst other data) contains a unique key for identifying customers. In your invoice table, you will
have a foreign key referring to these customers. When you make a selection from a list box, the "BoundColumn"
property reflects which column value of a result set should
be used as the value of the component. If the control is bound
to a database field, the column value is stored in the
database field identified by the property
Now, besides the result set the form is based on (all your invoices), the list box can be caused
to open a second result set, this time for the customer table, and fill it's list with entries
from this result set.
Additionally, it allows to model the relation between the two tables: When the user selects a customer from
the list, this customer has the unique id we just talked about (which is not necessarily visible to the
user in any way). The list box then automatically transfers this id into the foreign key column of
invoice, thus allowing the user to transparently work with human-readable strings instead of
pure numbers.
Let's call this result set the list is filled from the list result set here ...
The bound column property is only used if a list source is defined
and the list source matches with the types
Depending on the value of this property, the way the value of