What would you advise with the Choice of the designer of the database (for a beginner)?

Want to create a database (containing numbers, text, dates). As I see it (For the terminology apologies - not an expert).
The base consists of several "working" table + "reference".
1. Table 1 contains several columns of numbers with labels. It would be interesting to fill in manually and not part of a column copied from Excel (several dozen lines) and fill the rest manually (selection of books). Date avtozavodets.
2. For each of newly created rows Table1 Table2 lines are created (automatically, by "clicking") with autocomplete fields (from reference books), with the ability to edit these fields.
3. Generating Reports from the data of Table1 and Table2 in tabular form, all kinds of processing, filtering and calculations. With the ability to edit the data and save it into the database.
4. The ability to formulate Reports in Excel.
5. Preferably able multi-mode.
This is what I see as not an expert. Thanks for the help.
July 9th 19 at 10:54
3 answers
July 9th 19 at 10:56
from simple to complex

1) MS Access - all you can do once you've mastered VBA or even Python, and will be in the same prog (if available on the computer Access, of course)

2) Python + WEB interface, for example, in Django it is easier to do a lot of documentation + Python will poprostishe more VBA

3) PyQT

in 2 and 3 cases, you can do SQLite
July 9th 19 at 10:58
Database designer - I think such things are generally superfluous, confusing and pulls a lot of water. Paper and pencil + basic understanding of the RDBMS database, i.e. tables, relationships, triggers, queries, indexes = the most effective means.

Draw the rectangle A, then rectangle B, A and B write the major field bundles:
type Autokey int uniq here and there, draw 1:1, 1:*(1 to many), *:* (many to many) and arrow-vector who-with-whom is associated,
then write a clear plan of how the table And, for example:
When you insert to write a trigger that on the basis of data of reference C and d will create a record in table B, And duplicating:in the Autokey B.
When you delete a record from A trigger in A:Autokey deletes the records in B.
When a record is updated in A, updates the entry in B in A:Autokey.

etc.

All of these foundations support all (at least those that I know of) existing relational DBMS. What to choose?
Depends on how many users will have access to the database. One or more, if multiple access is parallel or one went, the second came (flew)?

Separate the design of the structure of your DB from visas. part.
You need to start specifically with what and how, will be stored in the database and how it will be interrelated.

At
A1. and 2.
Each database needs a reference with a unique numeric count index, such as Autokey.
Create таблицу1, as well with the index, and hang a trigger that works after the record is inserted in таблицу1, the trigger also having the data of the inserted record will see them record and reference will create an entry in таблице2., so, you don't need more button.

p 3., p. 4, p. 5: this is the visual part, and the relationship to databases has slightly more than nothing.

Use what you want to implement multi-window interface, all you need base - is queried.
If the report is simple, requires no macros, has hundreds of sheets, then why did you specifically XLSX format, when there is a simple CSV? To create simply and quickly.
July 9th 19 at 11:00
dbdesigner - web
MySQL WorkBench - Windows

Find more questions by tags DatabasesDatabase design