I have created a normalized Database:
I have a table with a key and Columns with Lastname, Firstname, Email, …
I have another table with the key of the first table and columns focused on something that they have done (i.e. paid dues).
I want to have a form that Allows me to search the First database to bring up particular members in the first database and then click on a button that adds a row in the second database based on the key from the first database.
The documentation I have read does not work. I have tried for 2 hours to follow the documentation and it doesn’t match what happens in the tool.
I was thinking I would create my own code in python but the documentation on that doesn’t seem right either.
Heck if I could just build content in python to manipulate the databases, I would take that. The simple straightforward stuff in LO is great, but as soon as I try to do something slightly complex I can’t seem to find documentation on it.
[Example] Relations reflected by list boxes in forms
More of that: Apache OpenOffice Community Forum - Database Examples - (View forum)
and particularly: Apache OpenOffice Community Forum - [Example] Invoice Forms (without macros) - (View topic)
Where is your problem. You are not limited to hsqldb or Firebird. Create your MariaDB, Sqlite etc database with any tool you like and connect LibreOffice to the result.
So create a macro for your button to add the line. With a macro you can even combine databases, but I guess you mean tables.
PS: As you don’t gave any details, I assume you only wished to vent a bit. There is a difference between asking for help or requesting pity.
This is the worst question I’ve ever seen, actually it’s not even a question. This is the guide - How to use the Ask site?
.
I imagine the documentation you refer to is Chapter 4 Forms. I have no idea how you jumped from two tables to two databases. Where is the simple file(s) demonstrating your issue?
Excuse me - I am sorry I offended you. I misused a term. I have two tables. I tried to follow the documentation you referenced, but what it told me to do didn’t seem to work. I get that my post was vague but so is the documentation. All I wanted to do was have a form that would allow me to search 1 table for the foreign key that I need to put into the other table.
I guess I shouldn’t be shocked that a community on the Internet is more interested in criticizing the poster than trying to understand what the persons problem is.
I know SQL. I have been able to do some pretty sophisticated coding over the years. I also have some programming experience and I have read a lot of the documentation. I try to do what the document told me to do (create a subform by dragging one form into another), I tried it a number of different way’s and couldn’t accomplish it. I then figured if the tool allowed by to write some code to access the database and write the content out (either to a form or even the screen) but there didn’t seem to be enough detailed documentation to do that either.
I am perfectly happy to follow some step by step advice on how to do either one of those things.
I was not looking for pity. I was looking for someone to tell me how to query 1 table to get the foreign key to put into another table. I apologize for not being clear enough in my question. I would love to create a form that allows me to find the key for an entry in table 1 and use it as the foreign key in table 2 (along with a could of fields of data for table 2).
The documentation told me to build a small table with a single field in it, create a form that has the query term in it and create a form that will contain the data retrieved from the query that finds the data in table 1 (including the foreign key) and make that form the subform of the form with the query on it. It told me to go to the navigator and drag the second form on the first but the tool wouldn’t let me do it.
I am willing to learn and try to step toward my full goal of creating a form that will put entries in table two based on the key in table 1. I would appreciate a little patience with me as I try to learn.
The basic filter-table i learned from this video (in german)
Above shows how to arrange form/subform in forms navigator. So you can create something to find your record in table1.
.
I think you ask as a procedurak programmer: Input, filter, get key, add line, …
But procedural does not work with sql.
You can choose your way and create a macro for the active part.
But that would be a wrapper for INSERT INTO table2
.
When you have only queries/SELECT, you may do a subselect and put it in a listbox to select a row from table1 and put the foreign key in table2.
Give me a break, it’s more than misusing a term that significantly affected your question, it’s about wasting the communities time and frustrating them by not taking the time to ask a question reasonably.
.
If you have issues with the documentation it would be helpful to advise what they are, even better if you can provide a revised version addressing any issues. I think the main issue is over-representing your experience and tying to jump in part way through the guide without taking the time to work through the example.
All this does not take a single line of macro code. A subform is filtered by its parent AND inherits default values for new records.
https://forum.openoffice.org/en/forum/viewtopic.php?t=56006
Sorry for the full quote. IMHO, this is a crucial statement:
In my early days with Base I resorted to macros rather quickly because I couldn’t wrap my mind around the combined utility of the available tools. After all, Base applications combine the [often hidden] features of an Office suite with those of a full-featured SQL engine – particularly when paired with HSQLDB 2.x. And coming from the MS Office automation environment, I was spring-loaded to workaround any perceived limitations or bugs using macros due to the ease of VBA in MS Office. Base, on the other hand, is a relatively primitive front-end with little ongoing development, and bugs that persist for years. The macro development environment is relatively difficult to learn due to a patchwork API and a very limited IDE by modern standards. Various add-ons to the IDE offer some welcome relief and critical features, but we still don’t have a modern, context-sensitive, development environment for Base/*Office. Other developments have smoothed the transition from VBA to *Office Basic. But it remains prudent to avoid extensive macro development with Base…at least initially. After all, we do see a tendency to use macros to overcome a poor database design/structure, which rarely turns-out well. In general, macros are a last resort in Base, and best used to refine the final workflow.
Fortunately, Base redeems itself with powerful Forms. The more I work with these Forms, the more I’m intrigued by the power of SubForms leveraging SQL. And the more I’m convinced that a proper database structure is the key to Base Forms, as well as, ongoing development and support. Several concepts are necessary to master SubForms, including a working knowledge of SQL code, relational database concepts (i.e. normalization), Form-Controls, the Base query-parser, along with Base limitations/bugs. This all takes some study and experience, but until you’ve mastered the potential of SubForms in Base, you really can’t determine when-or-where macros would be appropriate. There’s no replacement for hands-on experience, but macro-free examples such as these Forms can really speed up the learning process.