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.
Richard Kaye -----Original Message----- From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On Behalf Of Vince Teachout Sent: Wednesday, April 01, 2009 4:09 PM To: profoxt...@leafe.com Subject: Re: [NF] Unexpected SQL result - why? Richard Kaye wrote: > IIRC when VFP builds the result cursor, the SQL engine uses the values in the > first row it finds to determine the data structure. This can result in > truncated information. Yes, I'm pretty familiar with that, but I've only seen that where you're selecting from a field. With a VFP back-end, if you specify the length with a literal, it respects the length. This is what actually bit my colleague. This was code originally written by someone else for a VFP back-end, years ago, and it started to fail when the same SQL command was ported over to SQL Server. _______________________________________________ Post Messages to: ProFox@leafe.com 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/df1eef11e586a64fb54a97f22a8bd044153e7...@ackbwddqh1.artfact.local ** 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.
