I've seen this from time to time and usually is caused when the ClassIds in your project get hosed or the record that holds those ids gets fried. Internally I think the problem comes from an invalid class id or a duplicated classid and some sort of lookup internally into the registry fails in VFP.

Creating a new project will create new ClassIds and that should always fix the problem. If you're building EXE's though you'll want to be careful - creating a new project will create new ClassIds for the same ProgId which will result in duplicate DCOM entries which is a real pain. Samething happens with DLLs as well, but the dupes end up just dead unreferenced entries in the registry.

+++ Rick ---

>Suddenly I'm getting an "Invalid subscript reference." when I attempt to compile a project to a DLL. It rebuilds without errors, and I can create an EXE/APP fine, but as soon as I switch to either type of DLL I get this error during compilation. It compiled fine this morning!
>
>Steps I've taken already to fix:
>
>1. Created a new project.
>2. Restarted FoxPro
>3. Restarted Windows
>
>There's really only one PRG in the project, and that creates the OLE class.
>
>I'm about to restore from this morning's version, but I'd love to know what might be going on here!
>
>Thanks,
>
>Eric