Columns in forms!
- Thread starter geralf
- Start date
- Local time
- Yesterday, 22:46
- Joined
- Feb 19, 2002
- Messages
- 47,434
No, forms do not support columns the way reports do. I sent this request to the Access team last month but I doubt that it will make the next release but hopefully it will make the one after
Thanks Pat. I suspected that.
I have a table that lists 80 components in a production plant. My idea was to create a form that listed all these components. They will be colored after if they are working or not. Would be nice to make more than 1 column since the column width isn't any wide.
What about placing all the components as a field in a single form? The component list is quite stable, but changes will occur. The idea is also that if a component that isn't working is colored red. By double clicking on that component would bring up the stoppage history in a continous form. Could this be done or does this break any normalising rule that may cause problems later on=
TIA and thanks for your reply.
I have a table that lists 80 components in a production plant. My idea was to create a form that listed all these components. They will be colored after if they are working or not. Would be nice to make more than 1 column since the column width isn't any wide.
What about placing all the components as a field in a single form? The component list is quite stable, but changes will occur. The idea is also that if a component that isn't working is colored red. By double clicking on that component would bring up the stoppage history in a continous form. Could this be done or does this break any normalising rule that may cause problems later on=
TIA and thanks for your reply.
- Local time
- Yesterday, 22:46
- Joined
- Feb 19, 2002
- Messages
- 47,434
You might try making 5 subforms each based on a query that selects a range of componentIDs. This gives you a columns effect without denormalizing the database. Make sure that your selection ranges don't loose any component records. Let the criteria for the first be < a and the last be > d. The ones in the middle should be >= a and < b, >= b and < c, etc.
Yes! That's a great idea. The components are categorized in 15 categories. I won't have space for 15 columns but I guess I could place more than one subform in each column. If the users need to add new components, these will be added to the respective subform. It is more likely that we'll add new components rater than a category. OK now...15 subforms in a Main form (The Man form only has 1 record - to display the subforms' categories/components)
Can Access handle 15 subforms in a main form?
Thanks for the great idea Pat. I'll go for that one.
Can Access handle 15 subforms in a main form?
Thanks for the great idea Pat. I'll go for that one.
Last edited:
- Local time
- Yesterday, 22:46
- Joined
- Feb 19, 2002
- Messages
- 47,434
I've seen one form (created by an intern at a client company) that has around 30 tabs and each tab has 1-4 subforms. It was fine in A97 and only a little slow in A2K. So, try it. You should be fine.
