Thanks Naoto

I'll look into this just for interest, but I'm only using FOXTOOLS for GetFileVersion to check the EXE version, didn't realise that there's now a command that's part of VFP called AGetFileVersion thats does the same thing, so that makes FOXTOOLS redundant for me now and solves my problem.

>Have you checked where else you've got the FLL file -- especialy in directories listed in the PATH? I'd had many a head-scraching experience with the "wrong" DLL being loaded because of this. Another weird thing that could happen is when you've got the DOS APPEND command in effect (or anything of similar nature -- basically where PATH is used for executables, APPEND is for data files). When attached to Novell, the behavior was such that mapped drives behave as if you've got a APPEND in affect (so you may be surprised when you try opening a file that doesn't exist in the current directory, that a file on another drive with the same name would get opened).