Wow. My first question is why? That many elements on a single form throw up so many red flags for me. Some of the questions / concerns that come to mind are:
- This must be extremely difficult to administer as the developer
- If there are over 2k elements, how many fields does this table have and should some of these be split off onto a different table?
- There must be a rather complex business process this is trying to solve for
- Without seeing it, it sounds like it would be difficult / overwhelming for the users
I would suggest taking a hard look at the process you are trying to build on this form and see if there are ways that you can separate it into multiple forms.
Example 1: If you're trying to build out the form so that multiple roles can interact in different ways, you could create role-specific forms with only the elements specific to that role.
Example 2: If your form is trying to lead users through a step-by-step process, break the form apart according to the different steps. You would then be able to give your users a "Next Step" button that would appear once they saved the record. Clicking the button would open the same record in Edit Mode, but direct them to the next Form in the process. At the end, maybe they would save the record and be presented with a "Submit" button?
Example 3: If your form is that large because you are presenting the user with a lot of data, you can also break this up into multiple forms. Then, instead of using Tabs, you could set up a set of Navigation buttons that would direct the user to the various forms you've created.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------