- Supplier_ID
Supp1
Supp2
Supp3
Supp4
Supp5
Supp6
Supp7
Supp8
Supp9
Supp10
Supp11
Supp12
Which would give the following result .:
- Supplier_ID1
Supp1
Supp3
Supp4
Supp6
Supp9
Attaches a test file with data (Supplier_ID1 is manually entered)
I used the data you provided in your most recent speadsheet, but since you didn't provide part numbers I added some and imported them with the quantitues from the spreadsheet into Table1 and Table2. In addition to PartNumber and Quantity there is a field named ID, a Primary Key that was added during the import process. That is an index used by the database engine and is of no concern at this point.The basis for this consideration is two CSV files that contain approx. 6000 lines and two fields (article number and quantity)
so I added a table PriceList where I imported some of those details from your spreadsheet.Product group, supplier, VAT, price, etc. are added to each article (row)
This versatility makes a spreadsheet an expert tool, a quick scratch pad for users who precisely know what they are doing, what could go wrong and how to fix things when moving around cells having values or formulas referencing absolute references or relative ones.Albireo wrote: ↑Wed Jan 25, 2023 8:57 pm Offfopic.
- One reason is probably that it is so difficult/complicated to understand how to "get started" with Base.
- Another thing could be that it is so easy to copy / move / delete many records in a spreadsheet. Sorting can also work easily, with some limitations.
In other words: User interface, data representation, calculation and data storage are not strictly separated from each other which makes spreadsheets extremely difficult to use safely.[*]A third thing that can also be mentioned is the ease of creating tabs - easy to keep a result together in one file.
Base can be connected to existing databases of any type supporting either ODBC or JDBC. A database solution is just a database solution and "Base" is a tiny (and overly simplistic) set of tools to access some database from this office suite.[*]A fourth thought - There are not many companies (in Sweden?) that can be contacted to create a solution in OO/LO.
This is completely misleading. You can not learn database development by means of "guided tours" through a tiny addition of an office suite. Anybody who is familiar with any kind of relational database will find quick ways to plug a Base document to his/her existing database and add some meaningful user interface to the database using the little toolkit provided by this office suite. At the same time he/she may use the same database with some accounting software, customer relations, warehousing solution or with a web site. There is no such thing as a "Base database" until you use Base to create a new database from scratch. This special type of "embedded database" can't be used outside the office suite until you get it out of the cage.[*]A few years ago I tried to create a solution in Base. Asked questions in various forums - but Base was "dead". - got stuck and had to give up.
Now I don't know if Base has developed much in recent years.[/list]
Most guided tours are based on opening Base and creating a table directly in Base and showing some summary - So far no problems.
I'm 99% sure that the csv data you try to import into Calc had been exported from some database. Having imported database rows into an arithmetic calculator you feel discontent with the calculator's database functionality. In a database you have to define the column types before you append any data to the table. You are obliged to be the master of your database data before you add the first record. If you do not want any duplicates, define what a duplicate is and the database will reject storing duplicates. If you define completeness, completeness will be enforced. A data row is unique and complete with consistent data types or it will not be saved. This makes everything a lot easier to use, but you have to do all the work before storing the first row of data.But in many cases there is existing data to be managed and then it can be significantly more difficult (that's how I experience it)
What happens to duplicates? / empty lines?
Is 1234 (as text) the same as 1234 (as number)?
Will 0001 remain 0001 or just 1? etc.
This is why database development is a well paid profession. However, for what most people try to do on sheets so desperately, there will always be a simple database solution which takes some hours of design work but works for many users easily and reliably for decades.I have several projects that would be best solved with a database.
But don't know how some details could be resolved or where I can turn and reason about structures
Much is about some type of API - input/output from e.g. Base
Only Supp1, Supp3, and Supp6 are in both of the tables. Based on that list I would say that you want a list of suppliers found in either table.
You need a new topic for a new question. This one concerns analyzing two tables.
In SQL:MrProgrammer wrote: ↑Wed Feb 01, 2023 7:25 pm Based on that list I would say that you want a list of suppliers found in either table, not those found in both of them.
Code: Select all
SELECT "Name" FROM "ClientTable_A"
UNION SELECT "Name" FROM "ClientTable_B"
I would probably describe my desire to present all suppliers once - preferably in ascending order (but no requirement)MrProgrammer wrote: ↑Wed Feb 01, 2023 7:25 pm.... I would say that you want a list of suppliers found in either table, not those found in both of them.
Which ones?
I would say no. Given the way you've arranged the source data into "dual tables" there is no simple way to get what you'd like. You can only analyze data from dual tables with complex formulas, and perhaps using the Data → Consolidate feature. There are hundreds and hundreds and hundreds of Calc topics from people who split data into pieces and then want to analyze it. You will find that the solution is always: Don't segregate your data!