Show X amount of fields in a form
Greetings, Odd question. 1 table, 1 form. Within the form, a drop down menu and it has 1 through 100. The number represents how many objects. What I'm looking to do is that whenever the user selects...
Forum Discussion
Blake,
Here is an example.
A project has billables for each month. Each billable has Deliverables.
So, the table that has the billables has N amounts of deliverables. Instead of creating, say, 100, I was thinking if a drop down menu with numbers from 1 to 100 that when a user selects 89, it will create 89 fields.
At the begining I was thinking of creating 100 fields of deliverables in a child table. But then, I can only get summary fields from the child into the parent. That's one set back. Then, dynamic rule of show/hide would be large.
That's one scenario. The second scenario, say that we have 100 fields and each field is for each month starting to day and with 100 fields the last month would be something like in 8 years and 4 months in the future. Say 50% of deliverables are consistent and is month by month, one next to another, aligned. But some deliverables are separated, one in April, next in July, next in August, next in December. It is easy to just create 100 date fields, but then, again, it would be 100. If user can select, I need 17 fields to enter the deliverable dates, and forms shows 17 fields to be entered, it would be A BIG time saver, just imagine this case for over 600 projects and you'll get the picture of the time saved.
Here is an example.
A project has billables for each month. Each billable has Deliverables.
So, the table that has the billables has N amounts of deliverables. Instead of creating, say, 100, I was thinking if a drop down menu with numbers from 1 to 100 that when a user selects 89, it will create 89 fields.
At the begining I was thinking of creating 100 fields of deliverables in a child table. But then, I can only get summary fields from the child into the parent. That's one set back. Then, dynamic rule of show/hide would be large.
That's one scenario. The second scenario, say that we have 100 fields and each field is for each month starting to day and with 100 fields the last month would be something like in 8 years and 4 months in the future. Say 50% of deliverables are consistent and is month by month, one next to another, aligned. But some deliverables are separated, one in April, next in July, next in August, next in December. It is easy to just create 100 date fields, but then, again, it would be 100. If user can select, I need 17 fields to enter the deliverable dates, and forms shows 17 fields to be entered, it would be A BIG time saver, just imagine this case for over 600 projects and you'll get the picture of the time saved.