>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).

Thanks for the info, Gerry.

Oh, and while we're on the subject of Foxtools (and in case anyone out there cares), I should have a new version of the Extended Foxtools Help file out by the end of next month. As with the previous edition, I'll note which functions from the library have now (in one way or another) been included in the language proper and include documentation on any new functions.

(No, I haven't been able to download it yet from the MSDN site.:-( I've given up and am waiting on the next shipment.)