The way to approach this challenge is to change the data structure. Your example is violating the "First normal form" of database normalization. (Google "First normal form" and there are too many examples to understand the concept). You must change, from having multiple fields of the same subject in a record, to having a column with the subject field in a list. For example, in a person's table, you should not put multiple fields for home address, business address, alternate address, etc. What you should do is create an Address table related N:1 to the Person table. In this Addresses table there is a field with the Address and another to enter the Address type (Home, Work, Alternative, etc).

After the changes, when viewing a Person form, a list of records with the various addresses in a column will appear, instead of several fields with Addresses in the form.

2022-01-11
You need to change the structure of the database as advised above. If you don't change the structure you will have big scalability problems.