Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Rounding off of figures

Discussion in 'Information Technology' started by Graham, Jul 28, 2006.

  1. Graham

    Graham
    Expand Collapse
    Guest

    Just created a great database but when I imput some data in Access rounds it
    off to zero decimal places. Re-examined everything but can not see why it is
    doing this. ANY IDEAS?
    Thanks,
    Graham
     
  2. Loading...


  3. Allen Browne

    Allen Browne
    Expand Collapse
    Guest

    Open the table in design view.
    Select the Number field.
    In the lower pane, change the Field Size to Double.

    The Integer types store whole numbers only.

    --
    Allen Browne - Microsoft MVP. Perth, Western Australia.
    Tips for Access users - http://allenbrowne.com/tips.html
    Reply to group, rather than allenbrowne at mvps dot org.

    "Graham" <Graham@discussions.microsoft.com> wrote in message
    news:9AF998D5-C890-4467-B394-558EAABCB728@microsoft.com...
    > Just created a great database but when I imput some data in Access rounds
    > it
    > off to zero decimal places. Re-examined everything but can not see why it
    > is
    > doing this. ANY IDEAS?
    > Thanks,
    > Graham
     
  4. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    Most common cause is forgetting to change the Field Size of the field from
    the default Long Integer when you created the field. Only the Single and
    Double sizes can accept decimal points.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Graham" <Graham@discussions.microsoft.com> wrote in message
    news:9AF998D5-C890-4467-B394-558EAABCB728@microsoft.com...
    > Just created a great database but when I imput some data in Access rounds

    it
    > off to zero decimal places. Re-examined everything but can not see why it

    is
    > doing this. ANY IDEAS?
    > Thanks,
    > Graham
     
  5. KARL DEWEY

    KARL DEWEY
    Expand Collapse
    Guest

    What is the datatype of the Access field? Is it Number, Integer? If so, an
    integer is a whole number. You would need to use Single, Double, or Currency
    based on your requirement for precission.

    "Graham" wrote:

    > Just created a great database but when I imput some data in Access rounds it
    > off to zero decimal places. Re-examined everything but can not see why it is
    > doing this. ANY IDEAS?
    > Thanks,
    > Graham
     
  6. Terry Kreft

    Terry Kreft
    Expand Collapse
    Guest

    .... and decimal, but note that the decimal datatype is bit broken.

    Or use the currency datatype.

    --

    Terry Kreft


    "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
    news:u252vbbqGHA.1976@TK2MSFTNGP04.phx.gbl...
    > Most common cause is forgetting to change the Field Size of the field from
    > the default Long Integer when you created the field. Only the Single and
    > Double sizes can accept decimal points.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    > "Graham" <Graham@discussions.microsoft.com> wrote in message
    > news:9AF998D5-C890-4467-B394-558EAABCB728@microsoft.com...
    > > Just created a great database but when I imput some data in Access

    rounds
    > it
    > > off to zero decimal places. Re-examined everything but can not see why

    it
    > is
    > > doing this. ANY IDEAS?
    > > Thanks,
    > > Graham

    >
    >
     
  7. Pieter Wijnen

    Pieter Wijnen
    Expand Collapse
    Guest

    "Terry Kreft" <terry.kreft@mps.co.uk> wrote in message
    news:uQegyujqGHA.2452@TK2MSFTNGP03.phx.gbl...
    > ... and decimal, but note that the decimal datatype is bit broken.

    AKA buggy as hell
    Pieter

    >
    > Or use the currency datatype.
    >
    > --
    >
    > Terry Kreft
    >
    >
    > "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
    > news:u252vbbqGHA.1976@TK2MSFTNGP04.phx.gbl...
    >> Most common cause is forgetting to change the Field Size of the field
    >> from
    >> the default Long Integer when you created the field. Only the Single and
    >> Double sizes can accept decimal points.
    >>
    >> --
    >> Doug Steele, Microsoft Access MVP
    >> http://I.Am/DougSteele
    >> (no e-mails, please!)
    >>
    >>
    >> "Graham" <Graham@discussions.microsoft.com> wrote in message
    >> news:9AF998D5-C890-4467-B394-558EAABCB728@microsoft.com...
    >> > Just created a great database but when I imput some data in Access

    > rounds
    >> it
    >> > off to zero decimal places. Re-examined everything but can not see why

    > it
    >> is
    >> > doing this. ANY IDEAS?
    >> > Thanks,
    >> > Graham

    >>
    >>

    >
    >




    --
    ----------------------------------------
    I am using the free version of SPAMfighter for private users.
    It has removed 4282 spam emails to date.
    Paying users do not have this message in their emails.
    Get the free SPAMfighter here: http://www.spamfighter.com/len
     
  8. Jamie Collins

    Jamie Collins
    Expand Collapse
    Guest

    Pieter Wijnen wrote:
    > > ... and decimal, but note that the decimal datatype is bit broken.

    > AKA buggy as hell


    <Sighs> Here we go again...

    This week's news: the DECIMAL data type is worthy of consideration.

    Engine sorting of negative values in descending order (honestly, just
    how many people need to do this?) is predictable yet wrong. Resolution:
    don't sort using the engine or create an additional column for sorting
    purposes by efficiently promoting the DECIMAL column to another data
    type.

    Jet's CDEC casting function is broken but is not a major issue: Jet
    considers decimal values to be native DECIMAL in nature; the CDEC
    function can be implemented in VBA in Access; values in Jet can be
    coerced to DECIMAL by operating on them using native DECIMAL value.

    VBA has a Decimal variant subtype which is acceptable (and is numeric
    <g>): a multiple-scaled integer needed to implemented as a reference
    type; fixed point types have no hardware support so the inefficiency
    associated with the Variant type would still be an issue if Decimal was
    an intrinsic type; not all native Jet types map directly to a VBA type
    and where they do they are not always widely used (e.g. CHAR(N) maps to
    String * N).

    The export bug can be worked around (and improved upon) using a
    different export approach e.g. a query.

    Anything else?

    Jamie.

    --
     

Share This Page