Qrew LegendI do work with a few apps that have that number of fields on a single table, and that app uses legacy forms. I do know that as a builder, the loading of the form and making changes starts to get pretty laggy once you get over about 1000 fields.
My guess is on Legacy forms. It will perform fine for the users.
But having said all that if you're going into a brand new app with the plan to put that many fields on the form, then there is a good chance there's a better design with trial tables that will reduce the number of fields on the form. So I think you really got a question your architecture.
But if you thought that all through the architecture is right for your use case and I think it'll work fine on legacy Forums.
I have no idea how new style forms would behave with that number of fields
