can grow text box

[Todd]

I've got a report where I added a text box (call it signatures) in the detail
section. I've got an expression in the control source of the signature field
that shows certain fields if data is in them. The problem is that if the
certain fields (say 3 of the fields) all have data in them and the text box
field in the report is populated with them the report doesn't show all the
data. I set the Can Grow property to "Yes" but that doesn't seem to work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+" ") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5: '+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") & ('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave off the
fields that don't have anything in them. I did the expression because the
report would have alot of empty space if I actually had each table field on
the report.

Any suggestions?

 

[fredg]

I've got a report where I added a text box (call it signatures) in the detail
section. I've got an expression in the control source of the signature field
that shows certain fields if data is in them. The problem is that if the
certain fields (say 3 of the fields) all have data in them and the text box
field in the report is populated with them the report doesn't show all the
data. I set the Can Grow property to "Yes" but that doesn't seem to work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+" ") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5: '+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") & ('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave off the
fields that don't have anything in them. I did the expression because the
report would have alot of empty space if I actually had each table field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes did
you also set the Detail section CanGrow to yes?

 

[Todd]

The Can Grow for the detail section properties is also set to Yes.
--
Todd

I've got a report where I added a text box (call it signatures) in the detail
section. I've got an expression in the control source of the signature field
that shows certain fields if data is in them. The problem is that if the
certain fields (say 3 of the fields) all have data in them and the text box
field in the report is populated with them the report doesn't show all the
data. I set the Can Grow property to "Yes" but that doesn't seem to work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+" ") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5: '+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") & ('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave off the
fields that don't have anything in them. I did the expression because the
report would have alot of empty space if I actually had each table field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes did
you also set the Detail section CanGrow to yes?

 

[Todd]

FYI the other fields in the detail section of the report that I have set to
Can Grow work correctly where they wrap down to the next line.
--
Todd

The Can Grow for the detail section properties is also set to Yes.
--
Todd

I've got a report where I added a text box (call it signatures) in the detail
section. I've got an expression in the control source of the signature field
that shows certain fields if data is in them. The problem is that if the
certain fields (say 3 of the fields) all have data in them and the text box
field in the report is populated with them the report doesn't show all the
data. I set the Can Grow property to "Yes" but that doesn't seem to work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+" ") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5: '+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") & ('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave off the
fields that don't have anything in them. I did the expression because the
report would have alot of empty space if I actually had each table field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes did
you also set the Detail section CanGrow to yes?

 

[Ken Snell [MVP]]

Be sure that you do not have a Label on the same horizontal "plane" as that
textbox. Also be sure that you don't have any other controls on the same
horizontal "plane" where those controls are not set to grow.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/

FYI the other fields in the detail section of the report that I have set
to
Can Grow work correctly where they wrap down to the next line.
--
Todd

The Can Grow for the detail section properties is also set to Yes.
--
Todd

On Wed, 27 May 2009 09:32:01 -0700, Todd wrote:

I've got a report where I added a text box (call it signatures) in
the detail
section. I've got an expression in the control source of the
signature field
that shows certain fields if data is in them. The problem is that if
the
certain fields (say 3 of the fields) all have data in them and the
text box
field in the report is populated with them the report doesn't show
all the
data. I set the Can Grow property to "Yes" but that doesn't seem to
work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+"
") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5:
'+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") &
('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave
off the
fields that don't have anything in them. I did the expression
because the
report would have alot of empty space if I actually had each table
field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes did
you also set the Detail section CanGrow to yes?

 

[Todd]

Under the Format property for the signature field I had an > to make all
letters capital in that field. I took it out and the field started to wrap
correctly. What does the > have to do with the Can Grow property and how can
I still make all letters in the field capitalized? Would I just do it in the
actual table field?
--
Todd

Be sure that you do not have a Label on the same horizontal "plane" as that
textbox. Also be sure that you don't have any other controls on the same
horizontal "plane" where those controls are not set to grow.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/

FYI the other fields in the detail section of the report that I have set
to
Can Grow work correctly where they wrap down to the next line.
--
Todd

The Can Grow for the detail section properties is also set to Yes.
--
Todd


:

On Wed, 27 May 2009 09:32:01 -0700, Todd wrote:

I've got a report where I added a text box (call it signatures) in
the detail
section. I've got an expression in the control source of the
signature field
that shows certain fields if data is in them. The problem is that if
the
certain fields (say 3 of the fields) all have data in them and the
text box
field in the report is populated with them the report doesn't show
all the
data. I set the Can Grow property to "Yes" but that doesn't seem to
work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1: '+[sha1]+"
") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5:
'+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") &
('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and leave
off the
fields that don't have anything in them. I did the expression
because the
report would have alot of empty space if I actually had each table
field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes did
you also set the Detail section CanGrow to yes?

 

[Ken Snell [MVP]]

I've never run into the situation that you describe, so I have no suggestion
about why that would affect the wrapping.

However, try using a query for the report's RecordSource, where you replace
the signature field with a calculated field:

SignatureField: UCase([Signature Field])

Then bind that textbox to this calculated field from the query.
--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/

Under the Format property for the signature field I had an > to make all
letters capital in that field. I took it out and the field started to
wrap
correctly. What does the > have to do with the Can Grow property and how
can
I still make all letters in the field capitalized? Would I just do it in
the
actual table field?
--
Todd

Be sure that you do not have a Label on the same horizontal "plane" as
that
textbox. Also be sure that you don't have any other controls on the same
horizontal "plane" where those controls are not set to grow.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/

FYI the other fields in the detail section of the report that I have
set
to
Can Grow work correctly where they wrap down to the next line.
--
Todd


:

The Can Grow for the detail section properties is also set to Yes.
--
Todd


:

On Wed, 27 May 2009 09:32:01 -0700, Todd wrote:

I've got a report where I added a text box (call it signatures) in
the detail
section. I've got an expression in the control source of the
signature field
that shows certain fields if data is in them. The problem is that
if
the
certain fields (say 3 of the fields) all have data in them and the
text box
field in the report is populated with them the report doesn't show
all the
data. I set the Can Grow property to "Yes" but that doesn't seem
to
work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1:
'+[sha1]+"
") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5:
'+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") &
('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and
leave
off the
fields that don't have anything in them. I did the expression
because the
report would have alot of empty space if I actually had each table
field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes
did
you also set the Detail section CanGrow to yes?

 

[M Skabialka]

or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in Access
where a calculated field can't have the same name as an actual field)
Mich

I've never run into the situation that you describe, so I have no
suggestion about why that would affect the wrapping.

However, try using a query for the report's RecordSource, where you
replace the signature field with a calculated field:

SignatureField: UCase([Signature Field])

Then bind that textbox to this calculated field from the query.
--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/

Under the Format property for the signature field I had an > to make all
letters capital in that field. I took it out and the field started to
wrap
correctly. What does the > have to do with the Can Grow property and how
can
I still make all letters in the field capitalized? Would I just do it in
the
actual table field?
--
Todd

Be sure that you do not have a Label on the same horizontal "plane" as
that
textbox. Also be sure that you don't have any other controls on the same
horizontal "plane" where those controls are not set to grow.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/


FYI the other fields in the detail section of the report that I have
set
to
Can Grow work correctly where they wrap down to the next line.
--
Todd


:

The Can Grow for the detail section properties is also set to Yes.
--
Todd


:

On Wed, 27 May 2009 09:32:01 -0700, Todd wrote:

I've got a report where I added a text box (call it signatures)
in
the detail
section. I've got an expression in the control source of the
signature field
that shows certain fields if data is in them. The problem is
that if
the
certain fields (say 3 of the fields) all have data in them and
the
text box
field in the report is populated with them the report doesn't
show
all the
data. I set the Can Grow property to "Yes" but that doesn't seem
to
work and
the signature field width is as far as I can go on the report.

This is the expression in the control source: =('SHA-1:
'+[sha1]+"
") &
('Kobe 4: '+[kobe4]+" ") & ('Kobe 8: '+[kobe8]+" ") & ('MD5:
'+[md5]+" ")
& ('CDCK-16: '+[cdck-16]+" ") & ('CRC-32: '+[crc-32]+" ") &
('CRC-16:
'+[crc-16])

The expression will display whatever fields are populated and
leave
off the
fields that don't have anything in them. I did the expression
because the
report would have alot of empty space if I actually had each
table
field on
the report.

Any suggestions?

In addition to setting the text control's CanGrow property to Yes
did
you also set the Detail section CanGrow to yes?

 

[Ken Snell [MVP]]

or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in Access
where a calculated field can't have the same name as an actual field)
Mich

Thanks, Mich.... < groan > I've been spending way too much time with SQL
Server these days, and the idiosyncracies between the two keep overlapping
in my mind... SQL Server allows an alias to have same name as a field in a
source table/query.

 

[John Spencer]

Ah, but you can AS LONG AS you fully reference the field in the
function. The following works with no problem for me (untested in
versions before Access 2000).

Signature Field: UCase([TABLE NAME].[Signature Field])


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

or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in Access
where a calculated field can't have the same name as an actual field)
Mich

Thanks, Mich.... < groan > I've been spending way too much time with SQL
Server these days, and the idiosyncracies between the two keep overlapping
in my mind... SQL Server allows an alias to have same name as a field in a
source table/query.

 

[M Skabialka]

That's interesting to know - I was just speaking from experience where
sometimes things just don't work and the error messages are cryptic, and
using the same field name became something I avoided like the plague.
Mich

Ah, but you can AS LONG AS you fully reference the field in the function.
The following works with no problem for me (untested in versions before
Access 2000).

Signature Field: UCase([TABLE NAME].[Signature Field])


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

or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in
Access where a calculated field can't have the same name as an actual
field)
Mich

Thanks, Mich.... < groan > I've been spending way too much time with SQL
Server these days, and the idiosyncracies between the two keep
overlapping in my mind... SQL Server allows an alias to have same name as
a field in a source table/query.

 

[Todd]

Thanks for the help!!
--
Todd

That's interesting to know - I was just speaking from experience where
sometimes things just don't work and the error messages are cryptic, and
using the same field name became something I avoided like the plague.
Mich

Ah, but you can AS LONG AS you fully reference the field in the function.
The following works with no problem for me (untested in versions before
Access 2000).

Signature Field: UCase([TABLE NAME].[Signature Field])


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

or
SignatureFieldUCase: UCase([Signature Field])
so you won't have a circular reference (or whatever it is called in
Access where a calculated field can't have the same name as an actual
field)
Mich

Thanks, Mich.... < groan > I've been spending way too much time with SQL
Server these days, and the idiosyncracies between the two keep
overlapping in my mind... SQL Server allows an alias to have same name as
a field in a source table/query.