diff options
| author | Lionel Elie Mamane <lionel@mamane.lu> | 2013-04-21 19:32:05 +0200 |
|---|---|---|
| committer | Lionel Elie Mamane <lionel@mamane.lu> | 2013-04-22 17:55:44 +0200 |
| commit | eb387dcf416427d8ad415cde6186796cc6f2ae4e (patch) | |
| tree | e4f8dbc050b394fa98c6275b6ec3c10c67a029e5 | |
| parent | 1a19d124871079a80f0c93fe4478da66359de96d (diff) | |
Rephrase documentation a bit
Change-Id: Icb02894c32ced62792d641bf1177bdc2b5ba184b
| -rw-r--r-- | offapi/com/sun/star/form/component/DatabaseListBox.idl | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/offapi/com/sun/star/form/component/DatabaseListBox.idl b/offapi/com/sun/star/form/component/DatabaseListBox.idl index e77ee25184ca..d0070211368c 100644 --- a/offapi/com/sun/star/form/component/DatabaseListBox.idl +++ b/offapi/com/sun/star/form/component/DatabaseListBox.idl @@ -44,8 +44,8 @@ to enter invoices for your customers. Probably, you will have a second table (say <em>customer</em>), which (among other data) contains a unique key for identifying customers. In your invoice table, you will have a foreign key referring to these customers.<br/> - 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 <em>customer</em> table, and fill it's list with entries + Now, besides the result set the form is based on (all your invoices), the list box can be instructed + to open a second result set, this time for the <em>customer</em> table, and fill its list with entries from this result set.<br/> 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 |