How to Create A Sub - Form
My app is a project management tool for building Custom Homes. There are hundreds/thousands of design details that go into building homes and I need a way to track the design selections against an ac...
Forum Discussion
You might consider (1) using form rules to hide/show sections on an individual form and (2) create secondary forms to collect various related fields. Certain types of applications like insurance forms, loan forms etc can have an unending list of fields to collect as they ask everything under the sun. While the normal suggestion is to create child tables as Mark suggests this could get complicated in cases (like yours) where there are a lot of fields to collect.
Another suggestion is rather than create a child table for each of your 75 categories, you might be able to create fewer child tables if you abstracted the child tables to model a "feature list", "amenities list", "upgrades", or "pick list" rather than very specific child tables such as kitchen, bathroom, garage etc.
More than likely you will have to use a combination of (1) multiple sections, (2) multiple forms and (3) multiple child tables to get to a sweet spot balancing convince of data entry / navigation and performance.
Josh,
You can create alternate forms and you can easily make a URL formula button to switch between forms. But I would caution against this as it becomes awkward when you are viewing and edit the form to control which form to use. You users will get frustrated when editing that they are always on the wrong form when using the native EDIT button.
But if you do want to have alternate forms, you can make a URL formula button like this to switch forms.
to view:
URLRoot() & "db/" & dbid() & "?a=dr&rid=" & [Record ID#]
to edit
URLRoot() & "db/" & dbid() & "?a=er&rid=" & [Record ID#]
You can create alternate forms and you can easily make a URL formula button to switch between forms. But I would caution against this as it becomes awkward when you are viewing and edit the form to control which form to use. You users will get frustrated when editing that they are always on the wrong form when using the native EDIT button.
But if you do want to have alternate forms, you can make a URL formula button like this to switch forms.
to view:
URLRoot() & "db/" & dbid() & "?a=dr&rid=" & [Record ID#]
to edit
URLRoot() & "db/" & dbid() & "?a=er&rid=" & [Record ID#]