On Feb 6, 2008, at 11:02 AM, MB Software Solutions General Account
wrote:
> 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:
The single-letter problem would happen if you did something like this:
SELECT someField ... INTO CURSOR E
SELECT E
LOCATE FOR someField = someValue
If cursor 'E' is not in work area 5 (i.e., work area 'E'), you will
see the problem you describe, since 'SELECT E' is ambiguous.
-- Ed Leafe
_______________________________________________
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.
