It's been a while since I did this but I think that VFP contracts the column in it's cursor, it sees that it is a 0.00. So whey you go to use this for your own use you don't have full access of xx,xxx
That was in FP2.6 mind you so it may have changed in later versions. On Nov 12, 2007 6:50 AM, Rob Anderson <[EMAIL PROTECTED]> wrote: > Hi Alan, > > How about :- > select cast(0 as decimal(8,2)) as newfield into mytable > > HTH, > > Robbo. > > Rob Anderson | Software Engineer | Pegasus, an Infor company | t: +44 > 1536 495000 | d: +44 1536 495006 | f: +44 1536 495214 | > [EMAIL PROTECTED] | www.pegasus.co.uk > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Alan Bourke > Sent: 12 November 2007 10:58 > To: [email protected] > Subject: SQL Server aliased column from VFP > > Hi > > If you're selecting from a VFP table you can say: > > Select *, 00000.00 as newfield From MyTable Into Cursor MyCursor > ReadWrite > > > That will produce a field 'newfield' in the cursor with dimensions of > N(8,2). > > How would you reproduce that behaviour in T-SQL ? I only seem to get > back a field with 0.00 in it, which you can't enter anything greater > than 9.99 into, and replacing with something like 1234.56 puts 1235 in. > > > -- > Alan Bourke > [EMAIL PROTECTED] > > > [excessive quoting removed by server] _______________________________________________ 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.
