Hi John,

>I'd forgotten how much I hate using FOXTOOLS because you get "unknown function" messages during compilation (can you get rid of them?) and you have to remember where it is.

I've never had a problem with this. Since my framework relied (up until 6.0, I'm still evaluating the impact of the new additions) FOXTOOLS was automatically included in the project. By including it, FoxPro doesn't generate these errors, even though the file is marked as excluded. You simply have to remember to include the library when the setup disk(s) are created.

>Having got in a temper with it, I looked up the relevant calls in WIN32API.HLP and have put GetBuildNumber() in the "Files - WIN32API" download area.
>
>=GetBuildNumber("FRED.EXE") gets the build number of "FRED.EXE" with less fuss.
>
>Roll on September 2, of course.
>
I'll try to take a look at it today.