two columns leading nowhere

[barret bonden]

Subreport blues

Tyring to make a report that shows a list of names in two columns ; it's the
obvious need; it should start out with A to M or so in the
first colum and then run from N to Z in the second, on the same page. Saves
paper.

I cant get it to work ; I've played with page properties, setting the run to
"Accross then down", I get one column.
I've set "number of colums" at two. I've tried shortening the string, I've
tried prayer, almost.

 

[Duane Hookom]

Can you share something about column widths? I would expect you should use
down then across if you want the first letters in the first column.

 

[John Spencer]

When you set page set up to 2 columns, did you also change the Column Size
Width? If you have a column size width that is too wide to allow two columns
then you will still only get one column.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[Steve]

One way of doing it is to use two subreports. Base each subreport on a
query. In the first query set criteria for LastName to A to M and in the
second query set criteria for LastName to N to Z.

Steve
(e-mail address removed)

 

[barret bonden]

Thanks both of you for the ideas.
I've worked with setting the column size width to very short (and even
shortened the field size in the query)
When I make the column size width shorter I get a "half box" on the left
side of the report, with one column of data
on the left and nothing on the right side of the page.
I've experimented with setting "down and across" as well as "across and
down."

I've also see the whole right side of the report (not just the subreport
with my attempt at double columns) vanish from the
screen as it were, just leaving the left side with it's single columns, but
not all the time.
At the moment,in need and frustration, I've played with two subreports
with two queries , each calling half the alphabet,
(Like "[A-M]* and "Like "[n-z]*" ) but , of course, the columns are of
different lenght, as finding the exact middle of the data set wouild involve
a bubble sort (is ther a better way in Access ? ) which I would have to pass
to the query; I'd rather not bother, even if I can get it done.
I'd love to get this working as a standard two column report ! Help !

 

[barret bonden]

Steve:
Funny I just did that , and just posted it, prior reading your note.
Problem is Like "[n-z]*" and Like "[a-m]*" dont, in the social reality of
last names, produce the same number of records (or even close- it would
look silly to the client) , as I just discovered. Looks like I would have
to do a sort, find the middle and pass it to the query. Sounds like a slog,
given I must just be a click away (?) from getting a standard multi column
report from working.

 

[Duane Hookom]

"very short" has very little to do with two columns. The width is the
significant measure.

When you see one column down the left, does it show all the records or are
you missing the later ones? I would expect all records to display somewhere
but you haven't provided this key information.

If you want columns that automatically wrap 1/2 records on left and 1/2
records on the right, you will need to add a calculated column in your query
that identifies the first 1/2 and the second 1/2.

--
Duane Hookom
Microsoft Access MVP

Thanks both of you for the ideas.
I've worked with setting the column size width to very short (and even
shortened the field size in the query)
When I make the column size width shorter I get a "half box" on the left
side of the report, with one column of data
on the left and nothing on the right side of the page.
I've experimented with setting "down and across" as well as "across and
down."

I've also see the whole right side of the report (not just the subreport
with my attempt at double columns) vanish from the
screen as it were, just leaving the left side with it's single columns, but
not all the time.
At the moment,in need and frustration, I've played with two subreports
with two queries , each calling half the alphabet,
(Like "[A-M]* and "Like "[n-z]*" ) but , of course, the columns are of
different lenght, as finding the exact middle of the data set wouild involve
a bubble sort (is ther a better way in Access ? ) which I would have to pass
to the query; I'd rather not bother, even if I can get it done.
I'd love to get this working as a standard two column report ! Help !

When you set page set up to 2 columns, did you also change the Column Size
Width? If you have a column size width that is too wide to allow two
columns then you will still only get one column.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

.

 

[Steve]

Barret,

I don't think you ae going to get an even (or close) number of names in each
column in a standard multi-column report without telling Access where to
break the first column. I still think your best bet is two subreports. You
need to find criterias for the two queries that give you an even (or close)
number of names in each column. If it was me, I would try and find the
median of the primary key of the list of names then set the criteria of the
query for the first query to 1 to the median then set the criteria of the
second query to > the median.

Steve
(e-mail address removed)

Steve:
Funny I just did that , and just posted it, prior reading your note.
Problem is Like "[n-z]*" and Like "[a-m]*" dont, in the social reality
of last names, produce the same number of records (or even close- it
would look silly to the client) , as I just discovered. Looks like I
would have to do a sort, find the middle and pass it to the query. Sounds
like a slog, given I must just be a click away (?) from getting a standard
multi column report from working.

One way of doing it is to use two subreports. Base each subreport on a
query. In the first query set criteria for LastName to A to M and in the
second query set criteria for LastName to N to Z.

Steve
(e-mail address removed)

 

[Duane Hookom]

Only create one subreport (that has one column in page setup) and paste it
twice into your main report. The record source would be something like the
following that groups the records into two groups.

SELECT Int((Select Count(*) FROM tblUsers U where U.usrLogin
<tblUsers.usrLogin)*2/(SELECT Count(*) from tblUsers)) AS [Column], tblUsers.*
FROM tblUsers;

Your main report would need two text boxes:
Name: txtColLeft
Control Source: =0

Name: txtColRight
Control Source: =1

Use the link master/child properties of the subreport controls to link a
text box with the [Column] value in the subreports.


--
Duane Hookom
Microsoft Access MVP

Barret,

I don't think you ae going to get an even (or close) number of names in each
column in a standard multi-column report without telling Access where to
break the first column. I still think your best bet is two subreports. You
need to find criterias for the two queries that give you an even (or close)
number of names in each column. If it was me, I would try and find the
median of the primary key of the list of names then set the criteria of the
query for the first query to 1 to the median then set the criteria of the
second query to > the median.

Steve
(e-mail address removed)

Steve:
Funny I just did that , and just posted it, prior reading your note.
Problem is Like "[n-z]*" and Like "[a-m]*" dont, in the social reality
of last names, produce the same number of records (or even close- it
would look silly to the client) , as I just discovered. Looks like I
would have to do a sort, find the middle and pass it to the query. Sounds
like a slog, given I must just be a click away (?) from getting a standard
multi column report from working.

One way of doing it is to use two subreports. Base each subreport on a
query. In the first query set criteria for LastName to A to M and in the
second query set criteria for LastName to N to Z.

Steve
(e-mail address removed)


Subreport blues

Tyring to make a report that shows a list of names in two columns ; it's
the obvious need; it should start out with A to M or so in the
first colum and then run from N to Z in the second, on the same page.
Saves paper.

I cant get it to work ; I've played with page properties, setting the
run to "Accross then down", I get one column.
I've set "number of colums" at two. I've tried shortening the string,
I've tried prayer, almost.

.

 

[Steve]

Duane,

If there were an odd number of names, would you lose a name? That's why I
suggested working with the median of the PK.

Steve

Only create one subreport (that has one column in page setup) and paste it
twice into your main report. The record source would be something like the
following that groups the records into two groups.

SELECT Int((Select Count(*) FROM tblUsers U where U.usrLogin
<tblUsers.usrLogin)*2/(SELECT Count(*) from tblUsers)) AS [Column],
tblUsers.*
FROM tblUsers;

Your main report would need two text boxes:
Name: txtColLeft
Control Source: =0

Name: txtColRight
Control Source: =1

Use the link master/child properties of the subreport controls to link a
text box with the [Column] value in the subreports.


--
Duane Hookom
Microsoft Access MVP

Barret,

I don't think you ae going to get an even (or close) number of names in
each
column in a standard multi-column report without telling Access where to
break the first column. I still think your best bet is two subreports.
You
need to find criterias for the two queries that give you an even (or
close)
number of names in each column. If it was me, I would try and find the
median of the primary key of the list of names then set the criteria of
the
query for the first query to 1 to the median then set the criteria of the
second query to > the median.

Steve
(e-mail address removed)

Steve:
Funny I just did that , and just posted it, prior reading your note.
Problem is Like "[n-z]*" and Like "[a-m]*" dont, in the social
reality
of last names, produce the same number of records (or even close- it
would look silly to the client) , as I just discovered. Looks like I
would have to do a sort, find the middle and pass it to the query.
Sounds
like a slog, given I must just be a click away (?) from getting a
standard
multi column report from working.


One way of doing it is to use two subreports. Base each subreport on a
query. In the first query set criteria for LastName to A to M and in
the
second query set criteria for LastName to N to Z.

Steve
(e-mail address removed)


Subreport blues

Tyring to make a report that shows a list of names in two columns ;
it's
the obvious need; it should start out with A to M or so in the
first colum and then run from N to Z in the second, on the same page.
Saves paper.

I cant get it to work ; I've played with page properties, setting the
run to "Accross then down", I get one column.
I've set "number of colums" at two. I've tried shortening the string,
I've tried prayer, almost.

.

 

[Duane Hookom]

It works for me with an odd number (or even even).

Duane Hookom
MS Access MVP

Duane,

If there were an odd number of names, would you lose a name? That's why I
suggested working with the median of the PK.

Steve

Only create one subreport (that has one column in page setup) and paste
it
twice into your main report. The record source would be something like
the
following that groups the records into two groups.

SELECT Int((Select Count(*) FROM tblUsers U where U.usrLogin
<tblUsers.usrLogin)*2/(SELECT Count(*) from tblUsers)) AS [Column],
tblUsers.*
FROM tblUsers;

Your main report would need two text boxes:
Name: txtColLeft
Control Source: =0

Name: txtColRight
Control Source: =1

Use the link master/child properties of the subreport controls to link a
text box with the [Column] value in the subreports.


--
Duane Hookom
Microsoft Access MVP

Barret,

I don't think you ae going to get an even (or close) number of names in
each
column in a standard multi-column report without telling Access where to
break the first column. I still think your best bet is two subreports.
You
need to find criterias for the two queries that give you an even (or
close)
number of names in each column. If it was me, I would try and find the
median of the primary key of the list of names then set the criteria of
the
query for the first query to 1 to the median then set the criteria of
the
second query to > the median.

Steve
(e-mail address removed)



Steve:
Funny I just did that , and just posted it, prior reading your note.
Problem is Like "[n-z]*" and Like "[a-m]*" dont, in the social
reality
of last names, produce the same number of records (or even close- it
would look silly to the client) , as I just discovered. Looks like I
would have to do a sort, find the middle and pass it to the query.
Sounds
like a slog, given I must just be a click away (?) from getting a
standard
multi column report from working.


One way of doing it is to use two subreports. Base each subreport on
a
query. In the first query set criteria for LastName to A to M and in
the
second query set criteria for LastName to N to Z.

Steve
(e-mail address removed)


Subreport blues

Tyring to make a report that shows a list of names in two columns ;
it's
the obvious need; it should start out with A to M or so in the
first colum and then run from N to Z in the second, on the same
page.
Saves paper.

I cant get it to work ; I've played with page properties, setting
the
run to "Accross then down", I get one column.
I've set "number of colums" at two. I've tried shortening the
string,
I've tried prayer, almost.








.