Help with User input screen & underlying table.

[Neil07979]

All,

I want to build an input form for a number of users to capture timings of when activities are complete. Each of the activities are linked to a group, and each Group could have a different number of Activities (Pre defined).

The underlying table that I want to populate will be a simple table scruture and will contain the fields: date, Group, Stage, and Time (Among others) - so I will end up with duplicate Groups for each day - but with different stages linked.

The problem - I cant seem to get passed (Even before building) is how the input form - which I want the users to see all of the stages for that group on one singe form - will relay the information back to the table mentioned above.

I dont want to have to add each stage as a field in the table - as the number of stages could increase significantly.

Any ideas - or a point in the right direction would be great?

Thanks

 

[apr pillai]

I think you can use a Tab Control with different Pages for each group. The Tab Control Pages can be hidden by changing the Properties so that the User cannot select the Pages manually. You can test the CurrentUser of the Form and make the Page pertains to that User visible so that he can work on the fields placed on that page.

Check the link
http://www.msaccesstips.com/2007/06/control-screen-menu-design.shtml

to get a general idea as how to go about the designing task of Tab Control, to hide the pages etc.

 

[CEH]

Sounds like a bit more info is needed for anyone to give you a correct answer.... But if I am reading your post correctly.... You would have a table for "Groups" and a table for "Activities".... One Group can have many activities...So a one to many relationship.... your Activities table would have...date, stage and time.... maybe this would change with more info....

 

[stopher]

Sounds like a bit more info is needed for anyone to give you a correct answer.... But if I am reading your post correctly.... You would have a table for "Groups" and a table for "Activities".... One Group can have many activities...So a one to many relationship.... your Activities table would have...date, stage and time.... maybe this would change with more info....

I agree with Curtis. Sounds to me like you need two tables. Then you can apply the classic Form/Subform approach. The form would show the group and the subform would show the list of activities (stages?) for that group.

Chris