>... or try:
>
>SET LIBRARY TO ( HOME() + ".\FOXTOOLS.FLL" )
>
>or
>
>local lcTools
>lcTools = home() + ".\foxtools.fll"
>set library to (lcTools)
>
>The idea being, of course, to not assume that foxtools.fll is in the path, but to have specific knowledge of its location and express that in the string. Furthermore, if the quotes are presenting a problem then the parenthetical expression forces VFP to evaluate the contents of the expression prior to handing off the value to the SET LIBRARY TO instruction.

Larry,

People need to be careful about this. While it will resolve the problem at compile time, at runtime if the library isn't in the same location as the runtime library (usually the Windows System directory) the library won't be found. In order to avoid versioning problems, it's probably a better idea to place the library in the default directory for deployment purposes. The worst case scenario here is that you'd use SYS(5) + CURDIR() instead.