Richard Kaye wrote: > Actually the one I'm thinking of is when you use an expression like > firstname+' '+lastname to create a column. The width of the calculated column > is determined by the first matching row. The same thing can happen with > numbers, too.
Yes, I agree with that - I run into that often. To get around that, I PadR(firstname+' '+lastname, etc) to ensure I get a fixed width. And I know that if I had "Select Price from mytable", and the first price was 0.00, I'd get an N(4,2) result column, even if the next row had 999999.87. This case is different: It's a literal, not an expression: Select 000000.00 as mynumber from mytable. With a VFP back-end, I'll get N(9,2) as a result, with 0.00 in each, and I can store, for example, 123456.78 in a field with a SQL back-end, the same query gets me N(4,2) with 0.00 in each, and I can only store 1.23 in a field. So, it's as surprising to me if I had done Select "Bob Hopkins" as thename, and got back "Bob H", instead. I hope I was clearer this time. Thanks. _______________________________________________ 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.
