The precision of field "GARAGECARS" is probably less than
necessary to accomodate all values from the conversion in
your select statement. Find the precision and scale of
field "GARAGECARS" and try the select statement again
specifying precision & scale, for example ...
"GARAGECARS" is a NUMERIC(3,1)
Change your query to:
SELECT CONVERT(NUMERIC(3,1),LEFT(GARAGE,3)) AS GARAGECARS
FROM OLD_HOUSMAIN
If that fails then you need to increase the precision
and/or scale of the field.
>-----Original Message-----
>But the data type in question is numeric..
>
>Rich
>
>"Derek Shi" <drkshih.DeleteThis@hotmail.com> wrote in message
>news:012501c3c07f$8f847cb0$a001280a@phx.gbl...
>> It seems to me that the attribute in the table
>> Tablehouses is not accepting numeric data type. Try
>> changing the data type of the attribute.
>>
>> Derek
>>
>> >-----Original Message-----
>> >Hi,
>> >
>> >I am trying to move data from an old Access db into SQL
>> 2000.
>> >
>> >I have imported the old Access db into SQL and now I am
>> running queries to
>> >move the data from the old tables to the new tables. If
>> I run this
>> >statement:
>> >
>> >SELECT CONVERT(NUMERIC,LEFT(GARAGE,3)) AS GARAGECARS
>> FROM OLD_HOUSMAIN
>> >
>> >
>> >I get all 8025 records and no errors.
>> >
>> >If I try to run this statement:
>> >
>> >INSERT INTO TABLEHOUSES (GARAGECARS)
>> >
>> >SELECT CONVERT(NUMERIC,LEFT(GARAGE,3)) AS GARAGECARS
>> FROM OLD_HOUSMAIN
>> >
>> >I get this error:
>> >
>> >Arithmetic overflow error converting numeric to data
>> type numeric.
>> >
>> >Any ideas why? It seems to me that since the SELECT
>> statement executes on
>> >its own, the insert should as well. I've check and
there
>> are no null or
>> >empty strings in the old db..
>> >
>> >Thanks
>> >
>> >Rich
>> >
>> >
>> >.
>> >
>
>
>.
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Arithmetic overflow error converting numeric to data type ..