Decimal places doesn't seem to work

Laurel · External Since: Apr 02, 2004 Posts: 217

I have a report which displays some numbers. I choose "general number" as
the format, and "1" as the number of decimal places. But it displays up to
3 decimal places. Any suggestions?

TIA
LAS

Duane Hookom · External Since: Feb 07, 2005 Posts: 1359

What happens if you change the Format to Standard?

--
Duane Hookom
Microsoft Access MVP

"Laurel" wrote:

> I have a report which displays some numbers. I choose "general number" as
> the format, and "1" as the number of decimal places. But it displays up to
> 3 decimal places. Any suggestions?
>
> TIA
> LAS
>
>
>

Marshall Barton · External Since: Dec 07, 2003 Posts: 5120

Laurel wrote:

>I have a report which displays some numbers. I choose "general number" as
>the format, and "1" as the number of decimal places. But it displays up to
>3 decimal places.

It sounds like your number is a text string or was
concatenated into a text string. Post the text box's
control source and explain the data type of the field(s).

--
Marsh
MVP [MS Access]

Laurel · External Since: Apr 02, 2004 Posts: 217

That seems to work fine. How come?

"Duane Hookom" <duanehookom.DeleteThis@NO_SPAMhotmail.com> wrote in message
news:E3901B84-BE24-4115-878B-359CBF6CF08F@microsoft.com...
> What happens if you change the Format to Standard?
>
> --
> Duane Hookom
> Microsoft Access MVP
>
>
> "Laurel" wrote:
>
>> I have a report which displays some numbers. I choose "general number"
>> as
>> the format, and "1" as the number of decimal places. But it displays up
>> to
>> 3 decimal places. Any suggestions?
>>
>> TIA
>> LAS
>>
>>
>>

Duane Hookom · External Since: Feb 07, 2005 Posts: 1359

Different Formats afford different property settings.

From the answer to Marsh's reply, it looks like your table(s) might be
un-normalized.
--
Duane Hookom
Microsoft Access MVP

"Laurel" wrote:

> That seems to work fine. How come?
>
> "Duane Hookom" <duanehookom RemoveThis @NO_SPAMhotmail.com> wrote in message
> news:E3901B84-BE24-4115-878B-359CBF6CF08F@microsoft.com...
> > What happens if you change the Format to Standard?
> >
> > --
> > Duane Hookom
> > Microsoft Access MVP
> >
> >
> > "Laurel" wrote:
> >
> >> I have a report which displays some numbers. I choose "general number"
> >> as
> >> the format, and "1" as the number of decimal places. But it displays up
> >> to
> >> 3 decimal places. Any suggestions?
> >>
> >> TIA
> >> LAS
> >>
> >>
> >>
>
>
>

Laurel · External Since: Apr 02, 2004 Posts: 217

The control source is "Principle1" (one of 5, actually, Principle1,
Principle2, etc.). It is a column in a table of type Number, Single,
nothing in "Format." It is loaded by the following bit of code.

!Principle2 = isng_Principle2 / (ii_Principle2Count)

The other variables are "single" and "integer".

"Marshall Barton" <marshbarton.RemoveThis@wowway.com> wrote in message
news:ckq9b5pi9r3tkkjoj7pscqtmukpm746idb@4ax.com...
> Laurel wrote:
>
>>I have a report which displays some numbers. I choose "general number" as
>>the format, and "1" as the number of decimal places. But it displays up
>>to
>>3 decimal places.
>
> It sounds like your number is a text string or was
> concatenated into a text string. Post the text box's
> control source and explain the data type of the field(s).
>
> --
> Marsh
> MVP [MS Access]

Marshall Barton · External Since: Dec 07, 2003 Posts: 5120

I see that Duane's suggestion got you past your immediate
problem. Personally, I would use a specific format such as
#,##0.0
but that's just because I can not remember what the named
formats really do.

As Duane also mentioned, it looks like you might have bigger
problems with the table having inter-related fields, which
would be a violation of The Rules of Relational Database
Normalization (google it).
--
Marsh
MVP [MS Access]

Laurel wrote:
>The control source is "Principle1" (one of 5, actually, Principle1,
>Principle2, etc.). It is a column in a table of type Number, Single,
>nothing in "Format." It is loaded by the following bit of code.
>
> !Principle2 = isng_Principle2 / (ii_Principle2Count)
>
>The other variables are "single" and "integer".
>
>"Marshall Barton" wrote
>> Laurel wrote:
>>
>>>I have a report which displays some numbers. I choose "general number" as
>>>the format, and "1" as the number of decimal places. But it displays up
>>>to
>>>3 decimal places.
>>
>> It sounds like your number is a text string or was
>> concatenated into a text string. Post the text box's
>> control source and explain the data type of the field(s).

Vladimír_Cvajniga · External Since: Feb 01, 2007 Posts: 223

On 19 zÃ¡Å™, 19:34, Marshall Barton <marshbar... DeleteThis @wowway.com> wrote:
> I see that Duane's suggestion got you past your immediate
> problem. Â Personally, I would use a specific format such as
> Â Â Â Â #,##0.0
> but that's just because I can not remember what the named
> formats really do.
>
> As Duane also mentioned, it looks like you might have bigger
> problems with the table having inter-related fields, which
> would be a violation of The Rules of Relational Database
> Normalization (google it).
> --
> Marsh
> MVP [MS Access]
>
> Laurel wrote:
> >The control source is "Principle1" (one of 5, actually, Principle1,
> >Principle2, etc.). Â It is a column in a table of type Number, Single,
> >nothing in "Format." Â It is loaded by the following bit of code.
>
> > Â Â Â Â Â !Principle2 = isng_Principle2 / (ii_Principle2Count)
>
> >The other variables are "single" and "integer".
>
> >"Marshall Barton" wrote
> >> Laurel wrote:
>
> >>>I have a report which displays some numbers. Â I choose "general number" as
> >>>the format, and "1" as the number of decimal places. Â But it displays up
> >>>to
> >>>3 decimal places.
>
> >> It sounds like your number is a text string or was
> >> concatenated into a text string. Â Post the text box's
> >> control source and explain the data type of the field(s).

It must NOT be a violation of The Rules of Relational Database
Normalization, it may be a bug in Access. In some cases Access doesn't
recognize type of calculated fields in query. Especially if you use Nz
function; in such case you wil not be able to get decimal places, even
if you use Val(Nz(..., 0))! Similar behaviour with Switch, etc.
Generally, it's one of too many Access' bugs. Sad