It appears that you are using fields where you should be thinking in terms of records. Records can readily be created in browse mode and as needed by a user. Fields and tables cannot be.
I have a table that has a 'character' field and then i want the other fields to be the Act/Scene number i.e. 'A1S1, A1S2, A1S3......A2S1, A2S2.... ect. This I intend on showing as a list allowing quick editing of which character is in which scene.
These should be values all entered into the same field but in different records of the same table. You can even use two fields, one for the Act and one for the scene identifier. And such a table can be used in quite a few different ways for producing a list that permits Identifying which character is in a given scene.
I will create a new file for every show as they differ too much to be 1 database.
With a good solid relational design, I doubt that this will be the case.