Thanks for the reality check.

I couldn't find E documented either in the Type property for File objects so I just added it to my processing thinking it stood for scrEen not Form (although why form has a type K, I'll never know).

IAC, I'm not sure where I could do the E -> P conversion automatically. By the time the hook is instantiated the project table is already exclusively used and I don;t really want to institute a non-standard project. That could cause me other problems down the line. FWIW, the SPRs do show up the Program area so VFP thinks they are programs.

Thanks again.

>I've never noticed it before, but then again I don't think I've ever really used the project as an object, other than just playing. But, it is reproducable on projects that have been converted from 2.6 to 5.0 (then to 6.0). Looking at the project table, the Type field for .SPR files is listed as "E", which I can't seem to find documented anywhere. Programs are marked with a "P". I changed the Type field to "P" for all .SPR files, and they now show up in the Files collection. I don't know what the ramifications of changing the Type are, but maybe you could temporarily change it, then change it back?
>
>>Hi All,
>>The title spells it out but here is some more detail.
>>
>>I have an FPW project (yes, one of those) that was converted to VFP 3.0 then 6.0. However, not all of the code was converted. There is still extensive use of FPW SPR files. I have a project hook that runs through the Files collection and generates a report. The SPR files do not show up in the Files collection. Why not? The Files.Count property is off by the number of SPR files included in the project. They show up fine in the Project Manager itself, just not the COM collection.
>>
>>1. Has anyone noticed/experienced this before?
>>2. Is it a known bug? I checked on-line Technet but I might not have put in the correct keywords to get what I wanted.
>>3. If a bug, is there a workaround?
>>
>>Thanks for any information I can get.