Numerical Formatting in a Report

[bridgfod via AccessMonster.com]

Hello,

I am trying to whittle down some duplicate files on our server. One of the
lines in the report provides a summary of a particular duplicated file. In
the text box control, I have the following:

="There are " & [subCounter] & " additional copies of '" & [File_Name] & "'
potentially using up to " & [footsum] & " MB of space."

which works, but is ugly. The [footsum] entity is calculated by dividing the
file size in bytes by 1024 and again by 1024 to yield MB. Is there a way to
round the [footsum] calculation to 3 digits after the decimal, instead of the
14 or so that it wants to put there?

I did set the properties to "Fixed" and 3 decimals, and that worked when the
only thing that the textbox was putting out was the contents of [footsum].

Are there any switches that can be incorporated into the "& [footsum] &"
portion of the statement to control the formatting of this value?

Thanks,

Dale

 

[Al Campagna]

bridgfod,
Try inserting this into the concatenation...
.... & Format([FootSum],"#.000") & ...
--
hth
Al Campagna . Candia Computer Consulting . Candia, NH USA
Microsoft Access MVP
http://home.comcast.net/~cccsolutions

"Find a job that you love, and you'll never work a day in your life."

 

[Bob Barnes]

Similar question...no answer to yours.

I have...
=(Round([Text148]/([Text147]/60),2))

And set the Report Field to Fixed, 2 decimal places...but....
42.00 displays as 42
53.60 displays as 53.6.

Thoughts?

TIA - Bob

 

[Marshall Barton]

Similar question...no answer to yours.

I have...
=(Round([Text148]/([Text147]/60),2))

And set the Report Field to Fixed, 2 decimal places...but....
42.00 displays as 42
53.60 displays as 53.6.

Try setting the text box's Format property to:

0.00

 

[Bob Barnes]

Marsh,

Entering 0.00 converts by access to Fixed...didn't work.
Tried the "#.000" below and it didn't work either.

Thank you - Bob

Similar question...no answer to yours.

I have...
=(Round([Text148]/([Text147]/60),2))

And set the Report Field to Fixed, 2 decimal places...but....
42.00 displays as 42
53.60 displays as 53.6.

Try setting the text box's Format property to:

0.00

 

[Bob Barnes]

Al,

Entering 0.00 converts by access to Fixed (from Marsh)...didn't work.
Tried the "#.000" below and it didn't work either.

Thank you - Bob

bridgfod,
Try inserting this into the concatenation...
.... & Format([FootSum],"#.000") & ...
--
hth
Al Campagna . Candia Computer Consulting . Candia, NH USA
Microsoft Access MVP
http://home.comcast.net/~cccsolutions

"Find a job that you love, and you'll never work a day in your life."

Hello,

I am trying to whittle down some duplicate files on our server. One of the
lines in the report provides a summary of a particular duplicated file. In
the text box control, I have the following:

="There are " & [subCounter] & " additional copies of '" & [File_Name] & "'
potentially using up to " & [footsum] & " MB of space."

which works, but is ugly. The [footsum] entity is calculated by dividing the
file size in bytes by 1024 and again by 1024 to yield MB. Is there a way to
round the [footsum] calculation to 3 digits after the decimal, instead of the
14 or so that it wants to put there?

I did set the properties to "Fixed" and 3 decimals, and that worked when the
only thing that the textbox was putting out was the contents of [footsum].

Are there any switches that can be incorporated into the "& [footsum] &"
portion of the statement to control the formatting of this value?

Thanks,

Dale

 

[Marshall Barton]

Fixed should also work in this case.

I can't explain why, but what you're describing is the
effect of using format General Number. The only way I can
think of that happening is if your control source expression
is somehow being treated as a text value.
--
Marsh
MVP [MS Access]

Entering 0.00 converts by access to Fixed...didn't work.
Tried the "#.000" below and it didn't work either.

Similar question...no answer to yours.

I have...
=(Round([Text148]/([Text147]/60),2))

And set the Report Field to Fixed, 2 decimal places...but....
42.00 displays as 42
53.60 displays as 53.6.

Try setting the text box's Format property to:

0.00

 

[Bob Barnes]

Marsh,

The Field on the Access Report is..
=Format((Round([Text148]/([Text147]/60),2)),"Fixed")

I've tried all kinds of "Format"....something like 62.00
displays as 62, and 34.50 displays as 34.5.

IF we could only get the "Format - Cells - Number - 2
Decimal Places" like in Excel...

Could this be a "No Go"?? The Post before mine...tried
the same thing w/ 3 decimal places.

Thank you - Bob

Fixed should also work in this case.

I can't explain why, but what you're describing is the
effect of using format General Number. The only way I can
think of that happening is if your control source expression
is somehow being treated as a text value.
--
Marsh
MVP [MS Access]

Entering 0.00 converts by access to Fixed...didn't work.
Tried the "#.000" below and it didn't work either.

Bob Barnes wrote:
Similar question...no answer to yours.

I have...
=(Round([Text148]/([Text147]/60),2))

And set the Report Field to Fixed, 2 decimal places...but....
42.00 displays as 42
53.60 displays as 53.6.

Try setting the text box's Format property to:

0.00

 

[Marshall Barton]

The Field on the Access Report is..
=Format((Round([Text148]/([Text147]/60),2)),"Fixed")

I've tried all kinds of "Format"....something like 62.00
displays as 62, and 34.50 displays as 34.5.

IF we could only get the "Format - Cells - Number - 2
Decimal Places" like in Excel...

Could this be a "No Go"?? The Post before mine...tried
the same thing w/ 3 decimal places.

Well, that's not what I was suggesting, but it should have
worked.

What I was suggesting was to leave the control source
expression as: =Round([Text148]/([Text147]/60),2)
and set the Format **property** to 0.00 or Fixed.

But, either approach should produce the same result, which
they did in my tests.

Maybe someone else has an idea, but I can't explain whatever
is causing your problem.

 

[Bob Barnes]

From Marsh...

What I was suggesting was to leave the control source
expression as: =Round([Text148]/([Text147]/60),2)
and set the Format **property** to 0.00 or Fixed.

Marsh - That's what I tried...It's Access 2003 under Windows 2000.
I wonder if there's "any chance" the most recent Security Updates
(about 2 weeks ago) has affected this??? A fellow worker has said
his PC Apps have been adversly affected since the Windows 2000
Security Update 2 weeks ago.

We're willing to settle for this...what's our alternative??

Thank you..Bob

The Field on the Access Report is..
=Format((Round([Text148]/([Text147]/60),2)),"Fixed")

I've tried all kinds of "Format"....something like 62.00
displays as 62, and 34.50 displays as 34.5.

IF we could only get the "Format - Cells - Number - 2
Decimal Places" like in Excel...

Could this be a "No Go"?? The Post before mine...tried
the same thing w/ 3 decimal places.

Well, that's not what I was suggesting, but it should have
worked.

What I was suggesting was to leave the control source
expression as: =Round([Text148]/([Text147]/60),2)
and set the Format **property** to 0.00 or Fixed.

But, either approach should produce the same result, which
they did in my tests.

Maybe someone else has an idea, but I can't explain whatever
is causing your problem.

 

[Marshall Barton]

From Marsh...

What I was suggesting was to leave the control source
expression as: =Round([Text148]/([Text147]/60),2)
and set the Format **property** to 0.00 or Fixed.

Marsh - That's what I tried...It's Access 2003 under Windows 2000.
I wonder if there's "any chance" the most recent Security Updates
(about 2 weeks ago) has affected this??? A fellow worker has said
his PC Apps have been adversly affected since the Windows 2000
Security Update 2 weeks ago.

We're willing to settle for this...what's our alternative??

Since I have never used Win2000, I can not comment
intelligently on what, if any, problems exist in your
configuration.

Before going off on that kind of tangent, I would try
creating a new database with a simple form that tried to
reproduce the problem in the simplest situation you can
create. If that works, then start adding in a few parts of
your problem db until the problem reappears and you can
isolate the part that's causing trouble. If you can add
everything without getting the problem, then I guess you can
chalk it up to some kind of corruption.

 

[bridgfod via AccessMonster.com]

Al,

Thank you very much. That was exactly what I was looking for. Have a good
weekend.

Dale

bridgfod,
Try inserting this into the concatenation...
... & Format([FootSum],"#.000") & ...

Hello,

[quoted text clipped - 19 lines]

Dale

 

[Bob Barnes]

Me - not so smart...I hadn't set the Fixed 2 in the Detail Textbox...In
Design View,
I had Fixed 2 ONLY on the Group Footer.

Thank all of you (in "General Questions" also)..

Bob

From Marsh...

What I was suggesting was to leave the control source
expression as: =Round([Text148]/([Text147]/60),2)
and set the Format **property** to 0.00 or Fixed.

Marsh - That's what I tried...It's Access 2003 under Windows 2000.
I wonder if there's "any chance" the most recent Security Updates
(about 2 weeks ago) has affected this??? A fellow worker has said
his PC Apps have been adversly affected since the Windows 2000
Security Update 2 weeks ago.

We're willing to settle for this...what's our alternative??

Since I have never used Win2000, I can not comment
intelligently on what, if any, problems exist in your
configuration.

Before going off on that kind of tangent, I would try
creating a new database with a simple form that tried to
reproduce the problem in the simplest situation you can
create. If that works, then start adding in a few parts of
your problem db until the problem reappears and you can
isolate the part that's causing trouble. If you can add
everything without getting the problem, then I guess you can
chalk it up to some kind of corruption.

 

[Bob Barnes]

Me - not so smart...I hadn't set the Fixed 2 in the Detail Textbox...In
Design View,
I had Fixed 2 ONLY on the Group Footer.

Thank all of you (in "General Questions" also)..

Bob

bridgfod,
Try inserting this into the concatenation...
.... & Format([FootSum],"#.000") & ...
--
hth
Al Campagna . Candia Computer Consulting . Candia, NH USA
Microsoft Access MVP
http://home.comcast.net/~cccsolutions

"Find a job that you love, and you'll never work a day in your life."

Hello,

I am trying to whittle down some duplicate files on our server. One of the
lines in the report provides a summary of a particular duplicated file. In
the text box control, I have the following:

="There are " & [subCounter] & " additional copies of '" & [File_Name] & "'
potentially using up to " & [footsum] & " MB of space."

which works, but is ugly. The [footsum] entity is calculated by dividing the
file size in bytes by 1024 and again by 1024 to yield MB. Is there a way to
round the [footsum] calculation to 3 digits after the decimal, instead of the
14 or so that it wants to put there?

I did set the properties to "Fixed" and 3 decimals, and that worked when the
only thing that the textbox was putting out was the contents of [footsum].

Are there any switches that can be incorporated into the "& [footsum] &"
portion of the statement to control the formatting of this value?

Thanks,

Dale