Thanks, I had the scripting library in my Intellisense Manager listing, but I wasn't getting what I wanted - until you showed me your loop-in-loop.

Thanks!


>Steve,
>See Tamar's message. Add Microsoft WMI Scripting V1.X Library to the Intellisense Manager under Types - Type Libraries. You can then define a variable as

>local oService as WbemScripting.SWbemObject

>However, even if you do this, I don't think you are going to get what you want.
>
>A WMI object is a generic object with a property collection. You can access the collection via the Properties_ property of the object. The property collection holds a bunch of SWbemProperty objects. This object has a Name and Value property.
>
>I say this because Intellisense will not bring up a list of properties associated with a Win32_Service. It will only bring up PEMs associated with the SWbemObjectSet, SWbemObject, SWbemPropertySet and SWbemProperty.
>
>You can circumvent this limitation by inserting another for each loop inside the for each oService loop. Use:

>for each oproperty in oService.Properties_
>   ? oproperty.Name, oproperty.Value
>next

>
>HTH.