>
>George,
> Sorry.. This is a VFP 5.0a app.. Started out as a 3.0, but I changed that ^%#(^% real quick .. Funny thing is, one person can load it, but other people on different machines can NOT.. Maybe it is a rights issue?? I was thinking of making this file R/O, but didn't know if that would work..
>
>I also thought, okay I have a path statement setup for finding data tables (all free tables, to make sure the data can be accessed by 2.x based apps (Not My Idea, I have been told GOI ), So I thought to include the directory that Foxtools is located in the path and try that...
>
>I have no need for Foxtools right now, but in the future, I would like to be able to use it...
>
>There are prior versions of Foxtools available, so maybe I could just rename foxtools to something else, and try loading it that way, is that a possibility??
>
>Thanx for all your help..
>
>Tony Miller
>Vancouver, Wa
Tony,

It may very well be a rights issue. However, without knowing exactly what type of message the users who can't load it get, it's hard to say. In general, my users get all priviledges short of adminstration. I send an email to network adminstration telling them who, what directories and the rights they'll need.

You can't load a previous version, for example the one that came with 2.6, under VFP 5. Further, I don't think that whether the file's marked read only or not makes a difference.

The bad part about this is that you're stuck with additional code to maintain that's going to become obsolete with the release of the next version of VFP. As you may of read elsewheres on the UT, a number of functions that are currently in FOXTOOLS are going to be made part of the language in the next release.

George