Although it is true that you cannot include FLL files (or APP or EXE files for that matter) into you application, you can use a workaround.

Rename the FLL file into FoxFix.dat (or whatever) and include that file into the project under Text Files.
To access the FLL file in your code, copy the FoxFix.dat file into the Windows temp directory and restore the original extension:

LOCAL lcFoxFixFile
lcFoxFixFile = FORCEPATH("FoxFix.fll",GETENV("Temp"))
IF NOT FILE(lcFoxFixFile)
    STRTOFILE(FILETOSTR("FoxFix.dat"),lcFoxFixFile)
ENDIF
SET LIBRARY TO (lcFoxFixFile) ADDITIVE

>I am writing a program that uses FoxFix.FLL (a DBF repair routine) and as there is no information about distributing it along an app, either in the Hallogram web site (http://www.hallogram.com/foxfix/), where I purchased it, nor in the Xitech's (http://www.xitech-europe.co.uk/), and as I lost the documentation (I purchased it 13 years ago) decided to email Xitech, to the only email address that I found (sales@xitech.co.uk).
>
>As the email does not exists anymore, so I think, because I received Delivery Status Notification ("Delivery to the following recipients failed. sales@xitech.co.uk"), I would like to know what to do.
>
>Would I be infringing any copyrights, or anything else, if I distribute that componet with my app?
>
>Below is the email I sent to sales@xitech.co.uk:
>
>Dear folks,
>
>Back In 1999 I purchased a copy of FoxFix from Hallogram (http://www.hallogram.com/foxfix/), to be used when had corrupted files in my apps.
>Now I'm writing a program, that among many other operations, will have an option of correcting DBF files. This program is to be available for free among Visual FoxPro community.
>
>As FoxFix.fll must be present in the program's executing directory, even though it is included in the program's project, I ask you: can I put the FoxFix.fll together with the program for download?
>
>I thank you for your time, and hope to have your answer.
>
>Regards,
>
>Fernando Álvares (Brazil)