>>>>I am having a problem with an application I am working on.. I have a select group of people in a branch office testing this application, and some of them can NOT load Foxtools.Fll.. They are getting an error on the line that loads Foxtools..
>>>>
>>>>Is this a known problem, or is there something I can do (Besides the fact, that I have re-written all the functions that I use in Foxtools, with VFP code..)
>>>>
>>>>Thanx,
>>>>
>>>>Tony Miller
>>>>Vancouver, Wa
>>>
>>>Tony,
>>>
>>>I've never heard or encountered any problem with loading FOXTOOLS either in FPW or VFP. Further my guess would be that it's improbable that it would be a problem directly related to the configuration. There are a couple of possibilities, depending on the installation. The file could be corrupted. Another possibility is that the machine has more than one copy of the library on it and your application is trying load the wrong version. This could happen if the library is not in the start up directory, and another copy is on the DOS path. These are about the only things I can think of that would cause a problem like this.
>>>
>>>HTH,
>>>
>>>George
>>George,
>> What I have here is this.. One person running this app CAN run the app WITH Foxtools loading, but other people can NOT do this. I looked at what version of Foxtools were available out on their Lan (they also had FPW 2.x Foxtools) out there, but I had Foxtools loacted right with the exe. Next I literally hardcoded the path to where Foxtools was located, still no loading..
>>
>>I am just interested in why this happened, since I am looking at using a Framework (Visual FoxExpress) and I know they use Foxtools for somethings, and would not like to dump using it, just because of this reason..
>>
>>I did find one other person who had this problem, in the newsgroups, but he was not too much help, since they just stopped using the foxtools library too..
>>
>>Thanx,
>>
>>Tony Miller
>>Vancouver, Wa
>
>Tony,
>
>I've been a big user of FOXTOOLS.FLL ever since it came out. I've also been very gratified that some of the functions in it are to be included in the language in the next release. So not only do I have some experience, I have some partiality as well.
>
>Rather than hardcoding the path, I'd suggest using:
>
>SET LIBRARY TO HOME() + 'FOXTOOLS.FLL'
>
>This will assure that the version of the library is as you intend. Of course, you'll need to place the correct version of the library in the appropriate directory.
>
>FLL files are FoxPro specific. If an application can't load it, it suggests a larger problem.
>

George,
See my reply to Steve, along with the question of loading in a local directory for users, that I am using for temp files right now..

Thanx!

Tony Miller
Vancouver, Wa
>George