More than 1 column in continuous form?

[Guest]

Can that be done? If so, how?

 

[BruceM]

Yes. Add the field to the form is design view. For more details, please
provide more of a question.

 

[Guest]

Oh, cool. So all I have to do is put 2 text boxes next to each other on the
design page, and the records will be evenly split between the 2 columns?

 

[Guest]

Ok, that's not what I need.

Let me describe my situation a bit better:

I have a continuous from with 30 or so records. I would like to display
these records in a way so that the first 15 are shown in a left column, and
the second 15 in a right column.

 

[Rick Brandt]

Ok, that's not what I need.

Let me describe my situation a bit better:

I have a continuous from with 30 or so records. I would like to
display these records in a way so that the first 15 are shown in a
left column, and the second 15 in a right column.

There is no multi-column facility like that for forms. You would have to
use multiple subforms with some way for each to have a filter such that they
each only grab the appropriate records.

 

[Guest]

All right, thanks for clarifying that.

There is no multi-column facility like that for forms. You would have to
use multiple subforms with some way for each to have a filter such that they
each only grab the appropriate records.

 

[BruceM]

If this is for a report (i.e. for dsiplay or printing only, rather than to
interact with the data), you can design the report so that it occupies about
half of the finished width you want. Click View > Sorting and Grouping and
choose a field on which to sort the data. Click File > Page Setup, and
click the Columns tab. Enter 2 as the number of columns, then choose Down,
Then Across at the bottom of the dialog box.

If this is for a form in which the user needs to interact with the data it
gets more complicated. You would probably need to make two side-by-side
subforms, and adjust the record source of each one at runtime so that the
first one is the top 15 records and the second one picks up from there. If
this is your intention you would do better to post the question in the Forms
group.

 

[Guest]

Yes, this is for a data input form.
So I guess if I wanted this I'd have to make two subforms... ok. On the
upside, the record pool for this form is fixed so there wouldn't have to be
any dynamic adjusting.

Thank you.

 

[BruceM]

The tricky part of using two subforms is the recordset for the second
subform (16-30). Maybe you could use a Top 15 query for the first 15, and
for the second set of records you could make a Top 30 query, then base
another Top 15 query on that query. That Top 15 query would need to be
ordered in the opposite order from what is used in the first Top 15 query,
making it in effect a Bottom 15 query. I'm not sure what you mean when you
say that the record pool is fixed, or that there wouldn't need to be any
"dynamic adjusting", but if you mean the number of records doesn't change
that would make the task simpler. However, if that's what you mean it may
also mean there is no need to maintain anything other than current data,
which leads me to wonder if you would do better with Excel or Word. Of
course, I don't know the project details, so I am only speculating.

 

[Guest]

I have a questionnaire type application, with questions grouped by various
categories, and one category has a lot of questions that I want to display in
2 columns in order to save screen space. The categories themselves are
already portions of the entire pool of questions, so one more "category"
shouldn't make any difference.
I was thinking about using the actual question IDs to divide the form [ie. >
15 and < 15], but your idea sounds interesting as well. I'll look into it.
Thank you.

 

[BruceM]

Duane Hookum has a downloadable database called AtYourSurvey that could be
of interest:
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'

I haven't studied Duane's database, but as I understand it each question and
each response is a separate record, unlike the situation in, say, a form
used to collect Name, Address, etc., in which case each item is likely to be
a separate field in a single record. It sounds as if each question is its
own record in your project. If each question is a field in a single record
you only need to place controls bound to those fields onto your form
(although I don't think there is any way to do that with Datasheet view of
the form).
How you divide the records between subforms (assuming that each question is
a separate record) depends on the details of your data. Question numbers
could work in some cases, but there is no way to know from the available
information.

I have a questionnaire type application, with questions grouped by various
categories, and one category has a lot of questions that I want to display
in
2 columns in order to save screen space. The categories themselves are
already portions of the entire pool of questions, so one more "category"
shouldn't make any difference.
I was thinking about using the actual question IDs to divide the form [ie.15 and < 15], but your idea sounds interesting as well. I'll look into it.
Thank you.

The tricky part of using two subforms is the recordset for the second
subform (16-30). Maybe you could use a Top 15 query for the first 15,
and
for the second set of records you could make a Top 30 query, then base
another Top 15 query on that query. That Top 15 query would need to be
ordered in the opposite order from what is used in the first Top 15
query,
making it in effect a Bottom 15 query. I'm not sure what you mean when
you
say that the record pool is fixed, or that there wouldn't need to be any
"dynamic adjusting", but if you mean the number of records doesn't change
that would make the task simpler. However, if that's what you mean it
may
also mean there is no need to maintain anything other than current data,
which leads me to wonder if you would do better with Excel or Word. Of
course, I don't know the project details, so I am only speculating.

 

[Guest]

Yes, I've seen that database mentioned several times, and even pulled a copy
for myself. I have to admit though that it was too confusing for me.

You are right - each of my questions is a record in a table. There's another
Categories table, so it's easy for me to group questions by category. Adding
other criteria to the query sounds fairly straightforward to me.

Duane Hookum has a downloadable database called AtYourSurvey that could be
of interest:
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'

I haven't studied Duane's database, but as I understand it each question and
each response is a separate record, unlike the situation in, say, a form
used to collect Name, Address, etc., in which case each item is likely to be
a separate field in a single record. It sounds as if each question is its
own record in your project. If each question is a field in a single record
you only need to place controls bound to those fields onto your form
(although I don't think there is any way to do that with Datasheet view of
the form).
How you divide the records between subforms (assuming that each question is
a separate record) depends on the details of your data. Question numbers
could work in some cases, but there is no way to know from the available
information.

I have a questionnaire type application, with questions grouped by various
categories, and one category has a lot of questions that I want to display
in
2 columns in order to save screen space. The categories themselves are
already portions of the entire pool of questions, so one more "category"
shouldn't make any difference.
I was thinking about using the actual question IDs to divide the form [ie.15 and < 15], but your idea sounds interesting as well. I'll look into it.
Thank you.

The tricky part of using two subforms is the recordset for the second
subform (16-30). Maybe you could use a Top 15 query for the first 15,
and
for the second set of records you could make a Top 30 query, then base
another Top 15 query on that query. That Top 15 query would need to be
ordered in the opposite order from what is used in the first Top 15
query,
making it in effect a Bottom 15 query. I'm not sure what you mean when
you
say that the record pool is fixed, or that there wouldn't need to be any
"dynamic adjusting", but if you mean the number of records doesn't change
that would make the task simpler. However, if that's what you mean it
may
also mean there is no need to maintain anything other than current data,
which leads me to wonder if you would do better with Excel or Word. Of
course, I don't know the project details, so I am only speculating.

Yes, this is for a data input form.
So I guess if I wanted this I'd have to make two subforms... ok. On the
upside, the record pool for this form is fixed so there wouldn't have
to
be
any dynamic adjusting.

Thank you.

:

If this is for a report (i.e. for dsiplay or printing only, rather
than
to
interact with the data), you can design the report so that it occupies
about
half of the finished width you want. Click View > Sorting and
Grouping
and
choose a field on which to sort the data. Click File > Page Setup,
and
click the Columns tab. Enter 2 as the number of columns, then choose
Down,
Then Across at the bottom of the dialog box.

If this is for a form in which the user needs to interact with the
data
it
gets more complicated. You would probably need to make two
side-by-side
subforms, and adjust the record source of each one at runtime so that
the
first one is the top 15 records and the second one picks up from
there.
If
this is your intention you would do better to post the question in the
Forms
group.

Ok, that's not what I need.

Let me describe my situation a bit better:

I have a continuous from with 30 or so records. I would like to
display
these records in a way so that the first 15 are shown in a left
column,
and
the second 15 in a right column.

:

Oh, cool. So all I have to do is put 2 text boxes next to each
other
on
the
design page, and the records will be evenly split between the 2
columns?


:

Yes. Add the field to the form is design view. For more
details,
please
provide more of a question.

Can that be done? If so, how?

 

[Guest]

Ok, I went ahead and split my query in two, one showing the first 20 of my
questions, and the other the rest.

It works.

 

[BruceM]

Gald to hear it. I've never actually used that technique, except to test it
a little.