On Wed, February 6, 2008 11:52 am, Ed Leafe wrote: > On Feb 6, 2008, at 10:42 AM, MB Software Solutions General Account > wrote: > > >> Ed (or others) -- this is a good tip but did you actually see an >> instance where a single letter alias failed? > > > Of course, since I've had to deal with a LOT of legacy code. > > > The old 10-work-area systems used the first 10 letters of the > alphabet as aliases, and VFP 9 carries on that tradition. >
I think that's what's happening here. They do a SELECT INTO CURSOR above, and the field is definitely in their query field list, and then the line that fails is something like this: SELECT MyTable LOCATE FOR TablePK = MyCursor.TablePK The bug report is thrown on the LOCATE line, saying "Variable TablePK is not found." Yet when I go and create tests to try and replicate, I can't get the LOCATE command to fail in the command window at all. Here's my tests: ON ERROR CREATE CURSOR crap1 (cfield1 c(1)) CREATE CURSOR crap2 (cfield2 c(1)) SELECT crap2 LOCATE FOR cfield2 = crap1.cfield1 LOCATE FOR cfield1 = crap1.cfield1 LOCATE FOR cfield1 = crap1.cfield1 LOCATE FOR xx = crap1.cfield1 LOCATE FOR cfield2 = crap1.cfield2 LOCATE FOR cfield2 = crap1.cfield3 LOCATE FOR cfield2 = asdqwe ...which begs my followup question: how come I can't recreate the same error, even when the field doesn't exist on either side of the LOCATE arguments? _______________________________________________ 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.
