>I had forgotten about that. I never saw a reason to do it that way. I always shipped the .fxp or simply compiled everything into the exe.

Useful for components... but even then I guess I would use an .app file not a dll either.

I've had to use this though on code I didn't own where my app needed access to functionality compiled into the DLL. Worked...

-- Edit --
turns out that IN DLL doesn't work but IN APP definitely does. Must have had the APP file in the case above.

Either way it's still messy - there are some things that don't work very well when loading libiraries through apps because dependencies often don't work as all SET PROCEDURE STATEMENTS basically need to use IN APP or else they fail.

As you say - it's always easier to have the actual files in place and compile into the project.

+++ Rick ---

>
>>If I recall right you can do this though:
>>
>>

>>SET PROCEDURE TO SomeFile.prg in SomeDll.dll
>>

>>
>>A DLL is basically an APP file wrapped in a small DLL wrapper.
>>
>>+++ Rick ---