Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Le 23/02/2014 16:05, Jim Seymour a écrit :

Hi Jim,

A sub-form would (could?) be presented, allowing one to alter the
status table.

Btw: When I try to associate hdwr_assets.status_id to
hdwr_status.status_id using the Forms Wizard, execution results in

    Error: The data content could not be loaded.
    Error: SQL Status: 22023
     The column index is out of range: 1, number of columns: 0.
    Information: The SQL command leading to this error is:

     SELECT * FROM "public"."hdwr_status" WHERE ( "status_id"
     = :link_from_status_id )

How are your table indexes defined ? Are they "multiple column" indexes?

Which type of UI control are you using in your form to display the
result - Combobox or ListBox ?

You might be better off trying to do this manually rather than via the
wizard, i.e. in Form design mode using the Form Navigator to create your
subforms and then binding the corresponding data fields to UI controls,
as the subforms wizard hasn't always produced the expected results
throughout the various versions of LO.

At the moment, I can't tell whether this is a bug in the version of LO
that you are using, or whether it is a combination of other factors
(type of UI control in form, binding of data field to UI control, etc).

Alex T

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.