Dragan,

George already gave me advise to use it and put in VFPStart, which I did. I also put here several ON KEY LABEL command to simplify some of my usual tasks, etc.
Unfortunately, I haven't chance to take a look into your alert function after this. I'll do it in year 2000:) Anyway, some text file like readme would be also very useful...

BTW, if this library is so useful, why VFP doesn't include it by default? May be it should be in VFP7.0.


>> Then I tried to run Alert program from Dragan - just from curiosity. I just run it from WE and it also showed me an error - words function (which, I believe, belongs to FoxTools). And there is not readme txt file included! So, Dragan, I disappointed! :) It's very easy to check, why you didn't put it in your program?
>
>Well, if you want to use things that George or I do, you'd simply have to assume that Foxtools is loaded by default. Even with some of the path funcitons being moved into VFP proper, there are still many other functions I can't imagine living without, specially words() and wordnum(), which make my living far easier (and my code faster) when it comes to parsing parameters, chopping strings along arbitrary boundaries etc.
>
>The only place where I check if foxtools is loaded is the debugger - i.e. if I'm using something that someone else wrote, I look for the place where the ##%^^$% person unloads it without notifying me (this particularly goes to the authors of Visual ProMatrix 6, who deliberately load and unload foxtools within the main program before anything actually starts running - I hope they had no chance of hearing what I said when I discovered that).
>
>BTW, the two variables keeping the font name and size should be set by you, either somewhere in the calling program, or at the app level, or replaced with _screen.fontname and _screen.fontsize. You may actually play with setting them to various values before calling alert() and see how it works - I sometimes use rather large fonts to get the user's attention (of course, not always!).