>>Wanna really get ill? The following proves that AMEMBERS() doesn't work with SET STEP ON correctly - it ignores the two read-only properties. Try this with a glass of Bromo nearby:
>>
>>oShellObj = CREATEOBJ('Shell.Application')
>>?type('oshellobj') && Returns "O"
>>local x(1) && Creates single element array
>>a= oShellObj.Parent
>>a=oSShellObj.Application
>>y = amembers(x,oshellobj,1)
>>?y && = 23!!!!
>>?alen(x,1) && = 23!!!!!!
>>?alen(x,2) && = 2
>>?alen(x) && = 46 !!!!!!!!!!!!!!!!!!!
>>
>>
>>and if you examine the array, Application and Parent, both properties, appear from off-stage. Something's broke...
>
>Well, something definetly not right here, 'cause I only get the application, and parent back (y = 2). That's with STEP=ON or omitted in the config. I give! Three of us getting totally different results. Maybe I ought to consider a job in the Food Services Industry.< g >

Step through the code a line at a time in the debugger.

As far as FSI employment, as long as I don't need to use AMEMBERS() to get paid, I'll be happy to submit my resume for consideration!