A behavior change from VFP 8 to VFP 9 caused a RecNo() in a SELECT - SQL statement with a JOIN clause to randomly decide which table it gets the RecNo() from. Took me a while to understand why some customers were seeing a problem and we couldn't reproduce it. The code now uses PK's or some tough rewrite cases removed the JOINed table.
Happy hunting... Tracy -----Original Message----- From: MB Software Solutions General Account Sent: Thursday, March 20, 2008 4:03 PM (finally...a VFP post!) We've got a bug SOMEWHERE in this legacy code but it's a very difficult bug to recreate. iow, it only appears SOMETIMES and has no consistency whatsoever. This code creates a lot of temp tables locally (instead of cursors...why can I only guess that perhaps they didn't have cursors way back when in Fox or its predecessor...???), and often use "..., RECNO() as recno" as one of the fields. Are there any known gotchas in using RECNOs in a VFP SELECT-SQL statement? We're using VFP9SP1 but this is legacy code from many years ago, fwiw. tia, --Michael _______________________________________________ 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.
