why will vfp not create tlb

[cfsjohn]

I have many vfp projects. When I recompile all of them except one, vfp generates the executable, a vbr and a tlb. All of my projects contain at least one prg that defines a class as olepublic. That is why they all generate the tlb and vbr files. This one project generates the vbr but no tlb. Can someone tell me what may be wrong? The tlb is not open in some tool for looking at tlb's. The com server is not instanciated. Just no tlb.

 

[Chris Miller]

I cant tell why exactly. I think even just one native class set as olepublic with nothing defined additionally would create a tlb (type libarary), as een the base classes define a lot of public PEMS that contribute to the TLB.

I can recommend running VFP elevated, by setting the start shortcut properties: Shortcut->Advanced button-> check "Run as administrator".
That way when you compile you get OLE classes registered locally. I can't say if it helps creating the TLB file when building. But I assume once you run VFP that way, several things work better about ole servers in the project aside from the automatic local registering.

You could look into Project Info in the Servers tab what is listed and set there to maybe adjust something. Some options work with DLLs only, or even more specific MTDLL, others work only when building an EXE.

Chriss