Ed,

VFP can in general not "see" PEMs of a COM until the PEM has been accessed. It's kinda dumb that it doesn't read the TLB all at once when an COM is created. I know I'd have found it nice if it did while I was fighting my first Word automation project. Some things would just be easier if the debugger could show you all of the property values, but it only shows the ones you've accessed. Maybe it's a performance/resource issue of not attaching to a PEM until you need it. We could use an COMExposeAll (or maybe we could call it the COMFlasher method *G*) during development time.

>Nancy, AFAIK, VFP's AMEMBERS() won't pull out the information on the Shell.Application object - there are no writable properties or collections exposed directly by the object (the only properties exposed are Parent and Application, both read-only, both pointing to another Shell object.) At least I can't get AMEMBERS() to work on Shell.Application - I can run it against the shell objects returned by the two exposed properties, but they always return one entry, Application.