Forum Discussion
AviSikenpore1
8 years agoQrew Trainee
@Niraj - Are you just trying to enter that information in a single record in a table ?
You can either use a grid edit table or a many to many relationship using an intermediate table. So, what exactly are you trying to accomplish ?
if your set of questions/ crosstab is not going to change or expand over time you can bite the bullet and create 100 fields (10x10) and capture the values in a single form using alternate field labels. This method is not sustainable when the parameters of the cross-tab change.
You can either use a grid edit table or a many to many relationship using an intermediate table. So, what exactly are you trying to accomplish ?
if your set of questions/ crosstab is not going to change or expand over time you can bite the bullet and create 100 fields (10x10) and capture the values in a single form using alternate field labels. This method is not sustainable when the parameters of the cross-tab change.
NirajShah1
8 years agoQrew Cadet
@Avi. Thanks for your reply.
Here's what I am trying to accomplish: The columns in my picture represent categories of age ranges that are served by every activity (rows). Inherently, each row and column are related as for every activity a category will be served (the numerical variable) that goes in each box.
The thought process I've come up with so far is to create a table "Activities" and then have the relate that to "Categories" and have the user add a category for each Activity. Where I get stuck is how can the aforementioned relationship capture the fact that every activity will have a category. Would a many to many accomplish this?
For now, the set of questions / cross tab will not change, but they may later on. I know I can do this the tedious way by creating all the fields, but I'm sure there is an easier way that I am missing out on. I haven't use Q__B in a few years so pardon my unfamiliarity.
Here's what I am trying to accomplish: The columns in my picture represent categories of age ranges that are served by every activity (rows). Inherently, each row and column are related as for every activity a category will be served (the numerical variable) that goes in each box.
The thought process I've come up with so far is to create a table "Activities" and then have the relate that to "Categories" and have the user add a category for each Activity. Where I get stuck is how can the aforementioned relationship capture the fact that every activity will have a category. Would a many to many accomplish this?
For now, the set of questions / cross tab will not change, but they may later on. I know I can do this the tedious way by creating all the fields, but I'm sure there is an easier way that I am missing out on. I haven't use Q__B in a few years so pardon my unfamiliarity.