Roman Hausner wrote:
*) there is no direct support for many-to-many relations.
I wanted to solve this by having the subform edit the
many-to-many table and using a listbox to show the information
from the third table.
This worked as long as I had only one subform, but
when I added another (by copy-paste and changing the form
information), neither of the two forms worked any more.
The original form did not show any data any longer and
was totally unresponsive to clicks.
*) How do I add a subform to an existing form? I was unable
to find any function that does this. Adding a subform
in the form navigator did not show anything in the main form?
If I remember correctly, you had to make certain that the parent form
was the form that was selected, and then you needed to indicate the
field on which it relied. Perhaps I am not undertsanding, because I had
issues relating many-to-many relationships as well if I wanted it to go
both ways.
*) in the listbox control, what is the difference between
SQL and SQL (native)
I believe that this has to do to with escape processing. If you are
using a macro, then you can see the SQL that is actually sent to the
database.
*) in the listbox control, what is the "bound field" number
supposed to mean?
The BoundColumn specifies which column of the list result set should be
used for data exchange. In other words, 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
::com::sun::star::form::DataAwareControlModel::DataField .
For a value of zero 0, the selected (displayed) list box string is
stored in the current database field.
For a value of 1 or greater, the column value of the result set at the
position is stored in the current database field.
The bound column property is only used if a list source is defined and
the list source matches with the types
::com::sun::star::form::ListSourceType::TABLE ,
::com::sun::star::form::ListSourceType::QUERY ,
::com::sun::star::form::ListSourceType::SQL or
::com::sun::star::form::ListSourceType::SQLPASSTHROUGH . Otherwise the
property is ignored, as there is no result set from which to get the
column values.
*) What is the menu option tools->Relationships supposed to do
and why does clicking it tell me that my DB does not support relations??
I believe that this is supposed to indicate that one field is a foreign
key for another, or something like that.
Is there any documentation out there about how to get this done?
Hmm, I hope to write a book about it and the OOoAuthor web site has some
preliminary documentation that is FREE!
Do you think it is at all possible to get this done with OO?
I do not know.
I would really want to implement this in OO, but if it is not
possible I will have to deliver it for MS Access :/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.sxw
My Macro Book: http://www.hentzenwerke.com/catalog/oome.htm
Free Info: http://www.pitonyak.org/oo.php
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
