>>>>Neither would help because of the bug in the class. The message I referenced shows how to fix it.
>>>
>>>Actually, if he's following my original post, it would help (providing that it was foxtools that the application couldn't find). That's because I specifically mentioned the use of the ADDITIVE clause to keep from closing other libraries.
>>
>>No it wouldn't because of the following line in the class

>>SET LIBRARY TO HOME() + ".\FOXTOOLS.FLL"

wich woul kill your SET LIBRARY.
>
>OK, I see what you're saying here, and this would only seem to be a problem if different versions of the library would be in use or the library didn't exist in the location specified.
>
>I would seem to me, however, that, from my POV the value returned by the HOME() (or SYS(2004) for that matter) isn't exactly the best place for the library. Both of the functions return the location of the run-time library at run-time, rather than the actual start directory of the program.
>
>In most cases, this will point to the system directory. However, always placing the library there precludes the possibility of having different versions of VFP and the library in use simulataneously. For example, many people are in the process of upgrading to VFP 7.0. If multiple VFP apps exist on a given computer, it is most likely that all of them wouldn't be updated at the same time. Therefore, I would opt for using SYS(5) + CURDIR() or SYS(2003) to return the starting directory of the application itself and place the library there.

Hi George,

All you're saying makes perfect sense to me.