Tony,
Thanks! It seems that we had a variable declared as decimal 8,0 and the DB
Admin changed the field to 10,0 without telling anyone causing the overflow
to occur. Go figure! I guess it always pays to look at the data before
running programs. I'll pass this along to my programmers.
Thanks again for the help.
Drew Pollock
Atlanta, GA USA
At 09:19 AM 10/27/99, you wrote:
>
>Had this problem myselft the other day. My variable was defined as a
>smallint. I changed it to an integer and it fixed it.
>
>Are there limitations on the type of variable you are using? EG text
>variables....
>
>
>NOt sure if I have been of any help.
>
>Good luck.
>
>
>
>
>Tony Elson
>
>GIS Analyst
>
>Geographic Technologies Limited
>PO Box 6015
>Wellesley Street,
>Auckland, New Zealand
>
>Ph: 64 9 379 2061 x107
>Fax: 64 9 379 2044
>Mobile: 025 278 4896
>Email: [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>-------------------------------------------------------
************************************************************************
*****
*****NOTE THIS EMAIL ADDRESS HAS CHANGED
*****PLEASE NOTE THIS CHANGE BELOW
************************************************************************
[EMAIL PROTECTED]
=================
Atlanta, Georgia
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
