data type real 4

I have a value in a SQL table of -1.#IND for a data type of real 4. I am
wondering what the value of -1.#IND means.
--
Thanks Jeff DaunIt generally means you hit an issue with values using
approximate data types - there are some values where the
representation of the value gets hosed out. You will see
values along the lines of 1.#NF or 1.#ND for approximate
data types when you hit this in SQL Server.
-Sue
On Tue, 17 Jan 2006 09:26:06 -0800, Jeff Daun
<JeffDaun@.discussions.microsoft.com> wrote:
>I have a value in a SQL table of -1.#IND for a data type of real 4. I am
>wondering what the value of -1.#IND means.|||Thank you
--
Thanks Jeff Daun
"Sue Hoegemeier" wrote:
> It generally means you hit an issue with values using
> approximate data types - there are some values where the
> representation of the value gets hosed out. You will see
> values along the lines of 1.#NF or 1.#ND for approximate
> data types when you hit this in SQL Server.
> -Sue
> On Tue, 17 Jan 2006 09:26:06 -0800, Jeff Daun
> <JeffDaun@.discussions.microsoft.com> wrote:
> >I have a value in a SQL table of -1.#IND for a data type of real 4. I am
> >wondering what the value of -1.#IND means.
>|||I was wondering how would I be able to view the data in the column so that I
can find the value being put in the field from the application so that I can
find the correct precision to use?
--
Thanks Jeff Daun
"Sue Hoegemeier" wrote:
> It generally means you hit an issue with values using
> approximate data types - there are some values where the
> representation of the value gets hosed out. You will see
> values along the lines of 1.#NF or 1.#ND for approximate
> data types when you hit this in SQL Server.
> -Sue
> On Tue, 17 Jan 2006 09:26:06 -0800, Jeff Daun
> <JeffDaun@.discussions.microsoft.com> wrote:
> >I have a value in a SQL table of -1.#IND for a data type of real 4. I am
> >wondering what the value of -1.#IND means.
>|||I don't think so as it has a value that the SQL Server can't
represent. It's not really a matter of the precision as much
as a value getting in there that shouldn't have. If I
remember, the issue is due to SQL Server not fully
implementing the IEEE 754 standard for binary representation
of floating point numbers.
-Sue
On Wed, 18 Jan 2006 07:09:03 -0800, Jeff Daun
<JeffDaun@.discussions.microsoft.com> wrote:
>I was wondering how would I be able to view the data in the column so that I
>can find the value being put in the field from the application so that I can
>find the correct precision to use?