files is a collection of all the files in your project "_vfp.activeproject.files". Count is then number of objects in the files collection. itellesense should show you the objects.



>Yeah, I got that one. And I do see the Files object, but the only property it has is the Count. Yet, your code works. What is the logic of knowing to reference Files.Item[] ? I don't see a collection like that.
>
>>aaa is just a shortcut for the active project object.
>>aaa= _vfp.ActiveProject
>>aaa.files.count will give you the number of files in the project.
>>
>>
>>>Ok, that is very cool. I'll need to do a little research, but that looks like a winner.
>>>
>>>UPDATE: But where did you come up with the aaa.Files.Count and the aaa.Files.Item[] properties? I do not see them when I debug the _vfp.ActiveProject object.
>>>
>>>>How about this
>>>>

>>>>LOCAL laproclist[1],lavcxlist[1], lnRes, lnx
>>>>aaa= _vfp.ActiveProject
>>>>	
>>>>FOR lnx = 1 TO aaa.Files.Count 
>>>>	dd=aaa.Files.Item[lnx]
>>>>	DO CASE
>>>>	CASE dd.type = "V"
>>>>		lnRes = AVCXCLASSES(lavcxlist,JUSTFNAME(dd.name))
>>>>		*// Process here 
>>>>	CASE dd.type = "P"		
>>>>		lnRes = APROCINFO(laproclist,JUSTFNAME(dd.name))
>>>>		*// Process here 
>>>>	OTHERWISE
>>>>
>>>>	ENDCASE
>>>>NEXT 
>>>>
>>>>

>>>>
>>>>>>>We had, well, let's just say, a questionable procedure name popup on a client's PC as part of an error message. We now need a way to find all the procedure/function names in our system and review them. Any reasonably easy way to do that?
>>>>>>
>>>>>>Take a look at APROCINFO function to see if it helps you
>>>>>
>>>>>That was cool, but I need to traverse the entire project and files.