>Hiya-
>I know it was late last night, but I'm not insane. Truly! < s >
>
>

oShellObj = CREATEOBJ('Shell.Application')
>?type('oshellobj') && Returns "O"
>local x(1) && Creates single element array
>y = amembers(x,oshellobj,1)
>?y && = 21
>?alen(x,1) && = 21
>?alen(x,2) && = 2
>?alen(x) && = 42 

>
>If you're not seeing these results, then, well, may I offer that perhaps there is some tiny difference in what you are doing? BTW, I find that I have to execute each command in the command window separately.
>
>Some of the elements returned are:BROWSEFORFOLDER, CASCADEWINDOWS, TILEVERTICALLY.
>
>This is fun. When I type in
>

?oshellobj.settime

>in the command window, I get (surprise!) the Windows set time window.
>
>So, it seems pretty interesting to me. Whether it is useful for you, Pedro, I really don't know what you want to do with the shell object.
>
>Ed, I'd be interested in whether or not you tried my code sample?

Everything but the TYPE() statement; Dave Frankenbach pointed out that COM objects PEMs aren't visible until the object is actually accessed, which is presumably why the simplified CREATEOBJ() followed immediately by AMEMBERS() failed.

>
>>Nancy, AFAIK, VFP's AMEMBERS() won't pull out the information on the Shell.Application object>