>Hi Christof,
>
>>The only problem with the VFP help file is that the names are slightly different. In many instances they're truncated to 10 characters (_WFindTitle becomes _WFindTitl).
>
>Yeah, but DISPLAY STATUS gives you the proper name. At least that's what I use when I can't remember the right name and don't wnat to look up the text. :)

One of the reasons I wrote the help file was that I got tired of using that (and having to be careful about clicking the mouse or hitting a key). Made it a lot easier.:-)

>
>I don't know why this is, since it isn't a compiler limitation. In the VFP 6.0 version, for example, you have _WSockGetHostByAddr.
>
>Backward compatibility. FoxTools.Fll is almost unchanged between 2.6 and VFP and probably they didn't want to break existing code. BTW, even the VFP 6 documentation states that the name of a function cannot be more than 10 chracters, although since VFP 3 longer names are possible.

16 bit limitation, perhaps?

>>There are a couple of cases (well, at least one), where the parameter list is different. _GetWRect() is the one that comes immediately to mind.
>
>Haven't used that function yet.

It returns the absolute coordinates (left, right, top, bottom) of a form in relation to the Windows desktop, rather than in relation to the main FP window.