dll files

[Chris Wood]

When you bind a solution, you end up with 18 dll files which are automatically bound in. Depending on the type of file, what is in it, and where it will be used, are they all really necessary or can I leave some out. I am somewhat short of space and would like to reduce the overall size of my solutions.

Any Help??

Chris

[danjacoby]

The .dll files (in the Windows version only) are necessary, and must be included.

Any Windows application contains .dll files which are required in order to run the application. When you bind your solution, you are creating an application (that's the main file, which has the standard .exe tag for an application).

The Mac version, of course, doesn't have all these nasty .dll files.

[Chris Wood]

Yes I understand. However, two examples:

file FMPRT50.HLP is clearly a help file and there is no acess to a FilemakerPro help file in my kiosk solution.

Secondly, file clproof.dll is the spell checker and again there is no access to the spell checker in my solution.

I suppose the best thing to do is to delete the files one by one and see what happens

Chris

[john.daly]

You are quite correct that you don't need to include FMPRT50.HLP (this is not a dll) but you will need all the other dlls. Deleting even the cllroof.dll stops the solution from running.

[Chris Wood]

Thanks for the comments.

Chris

[David McKee (Protolight)]

If you want to know about the DLLs, just check out chapter 4 of the Developer's Guide, specifically page 4-2.

"Always remember...RTFM! - Read The FileMaker Manual."

-Dave

[Chris Wood]

Item 4-2 in the manual is Ok as far as it goes. But you need to know what XPAL files, MFC fiels, MSCV runtime file and MFC are?