Re: SQL Query - precision error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The value of f_doccumber can be any integar from 12000 up to 9999999999

I need to have a variable input from the user hence the ::f_docnumber::

"Kevin Spencer" wrote:

> Hi Art,
>
> What exactly is the value of f_docnumber?
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> ..Net Developer
> Sometimes you eat the elephant.
> Sometimes the elephant eats you.
>
> "Art" <Art@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A380A1E7-E75B-45B2-A759-814C0DE042E8@xxxxxxxxxxxxxxxx
> > The database is a runny under SQL 2000. We cannot change the precision as
> > itis software set.
> >
> > That said, why would I get a precision error when querying that database
> > from a Front Page query?
> >
> > If I run the query in Query Analyzer without the Front Page Search
> > variable,
> > it works fine.
> >
> >
> >
> > "Kevin Spencer" wrote:
> >
> >> Hi Art,
> >>
> >> Precision refers to the precision (number of digits, both to the right
> >> and
> >> left of the decimal point) in a floating point number. According to your
> >> field definition, the precision is 10, which means that you can store a
> >> decimal number with a maximum of 10 digits in it. The second number is
> >> scale, which is the number of digits allowed to the right of the decimal
> >> point of the number, which you've defined as 0 (IOW, you can store an
> >> integer with a maximum of 10 digits). I can't tell you much more, as you
> >> mentioned a "SQL table." SQL is a query language, and SQL Server is a
> >> database. Since a lot of non-database-professionals use the terms
> >> interchangeably, I don't know what kind of database you're using.
> >>
> >> --
> >> HTH,
> >>
> >> Kevin Spencer
> >> Microsoft MVP
> >> ..Net Developer
> >> Sometimes you eat the elephant.
> >> Sometimes the elephant eats you.
> >>
> >> "Art" <Art@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:97BDEFB4-A914-42A4-826A-85F2A115C7B0@xxxxxxxxxxxxxxxx
> >> >I am using a very basic query in Front Page 2002 against a SQL table
> >> >
> >> > SELECT * FROM tablename WHERE (f_docnumber = ::f_docnumber::)
> >> >
> >> > and f_docnumber is a search form field.
> >> >
> >> > When I run I get
> >> >
> >> > Description: The precision is invalid.
> >> > Number: -2147467259 (0x80004005)
> >> >
> >> > The field is defined in the table as numberic 9(10,0)
> >> >
> >> > Any ideas?
> >> >
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: SQL Query - precision error
    ... We cannot change the precision as ... > If I run the query in Query Analyzer without the Front Page Search ... >> decimal number with a maximum of 10 digits in it. ... >> Sometimes the elephant eats you. ...
    (microsoft.public.frontpage.programming)
  • Re: SQL Query - precision error
    ... Precision refers to the precision (number of digits, ... decimal number with a maximum of 10 digits in it. ... mentioned a "SQL table." ... Sometimes the elephant eats you. ...
    (microsoft.public.frontpage.programming)
  • Re: float bug? perl 5.8, DBI and oracle 10.2.0
    ... precision numbers in oracle, you've got 38 decimal digits to play ... and with minimal coaxing perl will handle them as ... digits from a 32 bit floating point number - I'll go out on a limb ... and hazard that one can expect 12 or so digits from a 64 bit floating ...
    (perl.dbi.users)
  • RE: float bug? perl 5.8, DBI and oracle 10.2.0
    ... I would not characterise 32-bit signed integers as giving 10 digits ... truncate and tell people you get 9 digits of precision. ... perl 5.8, DBI and oracle 10.2.0 ... Floating point values are typically stored in 64 bits or sometimes 96 ...
    (perl.dbi.users)
  • Re: float bug? perl 5.8, DBI and oracle 10.2.0
    ... I would not characterise 32-bit signed integers as giving 10 digits ... truncate and tell people you get 9 digits of precision. ... perl 5.8, DBI and oracle 10.2.0 ... Floating point values are typically stored in 64 bits or sometimes 96 ...
    (perl.dbi.users)