Stephen Russell wrote: >>>> Steve, an Integer field stores values from -2,xxx,yyy,zzz to >>>> 2,xxx,yyy,zzz so how would leaving it as a 8 byte char() work better? >>>> That's one digit less, if I understand you correctly. ??? >>>> >>>> Are you trying to multi-thread again? <g> >>> I thought that I was saying you could do the storage in char() and >>> have them do the conversion on their side for the data.Type() they >>> want to use. All you are presenting is storage. >> >> Then how do you represent 2,123,456,789 in a char(8) field using your idea? > ---------------------------- > > Backing up one more time. You are providing a container for > data/information. In this situation your int value is not large enough > to contain the value that your contractors want to save. > > Give them a char(25) column. All they have to do is a convert on > their extraction. I have to tweak back end data every once in a while > to fit my needs. It is no big deal. What kind of volume in rows of > data are you expecting? Will this data value be more then a pointer? > Will the data be in fact a legit measurable value? > >
I understand c(25) (or c(10)) would be big enough, of course...but you had said c(8) and so I wondered how you could make that statement. Thanks for correcting yourself and clarifying that. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
