>George,
>The project wasn't really converted. It's been rebuilt several times from scratch. When it was rebuilt, the project drew in the SPR files that were called but assigned a file type of 'E'. The problem I see (and Jonathan's response helped in this respect) is that VFP is looking at the type when it opens the project file and does not create a file object for those items.
>
>Separate but included in this is any of the Query... events of the projecthook class expects an object variable as the first parameter. If you have code in one of those (e.g. QueryModifyFile) and attempt to modify one of the SPR files, VFP throws a 'Data type mismatch" error because oFile is a logical.
>
>My contention is if its in the project file, the Files collection should have a reference to it. How big a deal could it be? Everything works normally except for the Project COM references.
>

I didn't completely understand how the project object was created. I assuming something here. The assumption is that the SPR files were included, but not the corresponding SCX/SCT files. If so, consider that the SPR is really no different from a prg, and if the SPRs were re-named with the prg extension they would be included. Another idea would be to use Refox to create the scx/sct files from the spr and use those instead.

I can understand both sides of this coin. The reason that they aren't being that VFP no longer uses SPRs, but as you said, "How big a deal...".

FWIW, I didn't find any listing for an "E" type in the 60PJX.FRX report.