(part 2)

Gene, about the alias thing:

If you have your table already open with something like this:

use ccli

Then you can re-open the same table under another alias this way:

use ccli alias *mytable again shared* ? *mytable*.clcode ... use in (select("mytable"))

Interesting things about this: - VFP does not create a second handle to the table, just reuse the existing one with another name - Because of that, the reopening with different aliases is the fastest way to reuse an already opened table - Each alias have it's own record pointer and can have it own index too, without interfering with the other aliases - Aliases allows you to encapsulate functionality for a group of tables that share one or more fields when you need to treat them the same way

2018-02-15 20:50 GMT+01:00 Fernando D. Bozzo fdbozzo@gmail.com:

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:

1. The way you know => &reference..referredto

2. Using evaluate => =Evaluate(reference + ".referredto")

3. 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.

I will 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]

Dne 24.2.2020 v 23:24 roger tremblay napsal(a):

I have a program which calls in excel (excel 2010) and it works well however with the advent of Excel 365  I can not make the call and get it to work below is the sample code used and it does work on 2010.  Any help would be appreciated.

thank you in advance

Roger

LOCAL loExcel loExcel = CREATEOBJECT("EXCEL.APPLICATION") loExcel.workbooks.open("C:\dev\BARNS\CLIP\BARCODE.xls") loExcel.visible = .t.

I think Excel365 has not COM interface.

FWIW works OK for me, Excel 1908 Click To Run.

Are you using 32-bit Excel?