Quote Originally Posted by prabhafriend
Batman, I will tell you a scenario for the need of dynamic forms/reports. Assume you have to track an attendance.
Which is the best design for an attendance?
Tracking the presence/absence? absence Right? Less occurence so less data.
So we just need to have an absent table. Absent table having date and emp.
Not sure I agree with your logic.

If you are tracking attendance then why not store attendance NOT absence?

Note: The volume of data should not matter in your normalization of the data. The volume of data will determine which back end database engine to use.


Quote Originally Posted by prabhafriend
But how the user here wants it. He needs an attendance form where we have to list all the employees in the first column. The we have to list all the dates in that month as fields. To mark presence/absence the user wants checkboxes in the intersection of each employee/date. Obviously, all checkboxes are ticked by default. If the user wants to mark an absence he just needs to unmark that checkbox.
I believe the design is perfect but see the requirement, it's complex.
I had a submit button. After making all the entries for every employee for that month the user will click the Submit, then I will compare the values of the controls (combo boxes dynamically created) with recordset. If the value differs I will insert a record in the absent table.
I know its not ethical. But otherwise we have to compromise the Design. If we go for recording the presence then we will have much data. Whats your opinion in this scenario?
from my experience, you have not described any needs that should require you to create controls dynamically at runtime.

I have done attendance systems that appear very much like a spreadsheet using check boxes. I used bound controls to a table and a form in datasheet mode. No need to create any objects on the form at runtime.