Re: The target for a numeric operation is too small to hold the resul t (C G D F)

[Eduard Sluis <eduard@xxxxxxxxxxxxxxxxxxxxxxx>]

Rob,
 
Now you try to make it ridicule.
But the question was not if you gonna lose something when you do a thing like 
that.
The question was how to be able to do so.
MOVE will definitely MOVE the field....  Agree?
If you do not want to lose a possible first digit??? You will not simply code 
one line!
 
Regards,
Eduard.

rob@xxxxxxxxx wrote:


So Eduard if I MOVE a 11,4 number like 1234567.8901 into a 10,4 field
wouldn't I get 234567.8901?  And you boss wouldn't mind the dropping of
$1,000,000?  I'd like to know the boss who that $1,000,000 was 'old
fashioned' and not needed.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


Hi,

Ok, I know, I'm old fashioned.
I just use 'MOVE'  (and have no problems).

Regards,
Eduard.

Scott Klement wrote:
Hi Ted,

> I have a similar situation where I have two different database fields.
> The result field is 10, 4 and the other is 11,4. Obviously too small,
> but what if you don't want to go around changing all of the database
> fields? Is there a routine anyone knows of to handle getting the result
> you want without having to change the db?

Are you asking for a routine that will allow you to fit an 11-digit number
into a 10-digit field? If so, there's no routine for that...

If not, what would you like to happen when you try to assign an 11-digit
number to a 10-digit field? I'm not clear on what the desired result is.
--



Implement-It,
Pos Cabai OfficePark unit 2,
Willemstad, Curaçao,
Netherlands Antilles.

Cell: 5999 5618980 Tel: 5999 7372031 Fax 5999 7372048