RE: Packed vs. Signed db fields

[rob@xxxxxxxxx]

I agree that the CSV is a better solution.  For example, I just ftp'ed a 
file defined as
CREATE TABLE ROB/JOEL (MYZONED NUMERIC (5 , 3) NOT NULL WITH
DEFAULT) 

INSERT INTO ROB/JOEL VALUES(2.5)
INSERT INTO ROB/JOEL VALUES(-3.7)

Now, upon arrival I have:
02500
0370}

If they code for this hardcoded assumption of decimal places and you 
change your field sizes on the 400, they're in for an unpleasant surprise. 
 And who wants the hassle of coding for that sign?

Then again, if you even change the size of text fields all their positions 
are off.  Therefore not only will they lose data on that field, but 
they'll lose the values of all remaining fields.  And I am working with an 
ERP package that changed the field size to even key fields in their files, 
(like the key to their item master).  And y'all know how slow to change 
ERP vendors are.  If they can do it, others will.

Then again, CSV can even bite you if they insert a field in the middle of 
the mix.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin