>>Do you use HOME() or Foxtools.fll anywhere in the project?
>
>You may be onto something. Exactly what, I don't know. Not HOME() (as far as I can remember), but Foxtools. When I place the library in the same directory as the script. It works properly. When it's not there it doesn't. The first ERROR statement is by-passed. Why? I dunno.
>
>But further, if the library isn't loaded (in the Init), then the object shouldn't instantiate. It does, however.

Here's something I found out about VFP and FoxTools the other day:

- If you have multiple FOXTOOLS in your path (I had versions 6.0 and 7.0), VFP will search until it finds a "valid" one. (I was switching between 6.0 and 7.0 in the same directory; FOXTOOLS 7.0 was in my working directory; I had become convinced that it worked with both versions ... not so).

- If VFP does not find a "valid" one (even if there is a FOXTOOLS in the path), it issues a "missing/not found" message (as opposed to an "invalid library" message). I think this is the case when you don't code a fully qualified name.

Anyway, I often do a search of all my drives for my Project components and insure that something isn't taking precedence when I'm not expecting it (FLL, DLL, EXE, whatever).