Gene, you did talk about objects, not tables and fields. They are not treated the same way.
In this case, then Ted is right, the alias must be used.
You can use generically with something like this:
use ccli alias *mytable* ? *mytable*.clcode
Nice thing about aliases is that you can use the same alias for any table in the case that those tables have the same fields you want to access.
2018-02-15 20:16 GMT+01:00 Gene Wirchenko genew@telus.net:
At 11:07 2018-02-15, Gene Wirchenko genew@telus.net wrote:
At 10:57 2018-02-15, "Fernando D. Bozzo" fdbozzo@gmail.com wrote:
To talk with an example, if you have this:
oObj = createobject("custom") reference = "oObj"
The you have at least 3 options:
The way you know => &reference..referredto
Using evaluate => =Evaluate(reference + ".referredto")
My preferred: Caching the object and then using it:
oRef = Evaluate(reference) ? oRef.refered1 ? oRef.refered2 ...
I was hoping to avoid evaluate(), but your third way makes sense. Iwill check if it works in all the contexts I am thinking of. (I was using "object" and "reference" rather loosely.)
Unfortunately, it does not work in my usual use case: as an alias.Example: use ccli where=evaluate("ccli") && Nope ? where.clcode
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]