List of tables in form

[ReallyGoodUser]

Hi everyone from northern Russia!
I have a database structure as in Figure 1 in the attachment.
I want to create a form that allows editing the parent table level_one and the child table level_two at the same time.
There are many of the same fields in the level_one and level_two tables, in my opinion the best way to create the form as shown in Figure 2 in the attachments.
The problem is, I don't know if there is a way to create such list of tables in Access.
Photo 3 in the attachment describes my vision of the completed form.

 

[The_Doc_Man]

Based on your post count, this is your first post. Welcome to the forum.

Depending on the comment about "same fields in level one and level two tables" you might have an incorrect data structure. Properly normalized data should only need to be stored in one place and merely referenced via JOIN queries where needed in other places. You could be right in your structure but we can't tell that. It might be easier for us to give you "best advice" if we know in English what you were trying to do. Pictures don't ALWAYS fully convey purpose, and given the possibility of some issues with your structure, it might be hard for us to guess.

Your diagram in screen1 shows another problem. Access really doesn't like having two paths from point A to point B but you have that. When Access has an ambiguous path (relationship) then it gets confused when trying to build queries that somehow relate the tables at the ends of the two paths because it doesn't know which relationship to exploit.

 

[ReallyGoodUser]

Based on your post count, this is your first post. Welcome to the forum.

Thank you! This forum is great!

an incorrect data structure

Yes. But this cannot be changed, because the hierarchy of levels must be clearly traced in the structure of the database - this is the task that was given to me at the university. Other structure will not be accepted.

what you were trying to do

This is a checklist. For example:

• Checking the security of the territory ---- [first level]
  • Installed a fence around the perimeter ---- [second level]
    
  • The territory has an autonomous power source ---- [second level]
    
  • There are no industrial facilities nearby ---- [second level]
• Checking the economic security of the enterprise ---- [first level]
  • The order of document flow has been established ---- [second level]
    
  • No debts to shareholders ---- [second level]

At the first level, a general conclusion is made. At the second level, each criterion is checked. The database contains regulatory documents, methodological documents and much more.

Access really doesn't like having two paths from point A to point B

Oh, I didn't know about that. How can I solve this problem with this kind of database structure?

 

[arnelgp]

i made a sample. maybe it will help (or not).
i made 2 tables (masterchecklist and subchecklist).

add the second level on the lower subform.
you should number them starting with 1 (meaning the position on the list0.

 

[ReallyGoodUser]

@arnelgp thank you! This is what I need too! To be honest, I was considering having two tables linked by parrent_id, but I was hoping there was a way to create a subtable in each row of parrent table, as in Figure 2 in the top of thread.

 

[Pat Hartman]

If arnel's solution works for you, fine. But the structure you started with allows anomalies. Notice how the records in table_One_files conflicts with table_two_files.

.