>>Quick question. FindWindowEx() requires the class name of the window be passed. The documentation, however, doesn't mention whether or not in can be NULL, so I assume that it can't be. Now getting the class name of the main VFP window isn't a problem. However, I've noted (using Spy++) that not all the class names of the windows match the parent. Admittedly, I haven't researched this very carefully. So the questions are: Can the class name be NULL, and if not, are all the form's class names the same as the parent?
>>
>>TIA,
>
>FindWindow requires a class name as it's first parameter as well. I declare it an integer and pass 0. Just musing, I wouldn't think that all of the class names would necessarily be the same as the parent.

Passing the 0 is the passing a NULL. And I think I've answered my own question. The FindWindow doc doesn't mention that you can pass a NULL with it either, only with the title bar. As far as the class names themselves, some are some aren't.
>

>Thanks for the info on Foxtools. I have used it years ago with FPD/W because it was almost necessary. <g>
>
>I think that it would be cool if VFP decided to support the lib extentions. It would also be nice if the API functions were implemented a bit further. Despite all of the research that I have done, classes I've looked at, I still have trouble with structs and VFP. I just gave up.

I think so too. I wish they had a function like the old VARPTR() in BASIC that returned the memory address of a variable. I know VB now supports an "AddREssOF" operator for API callbacks.

Don't give up on the structs, some (especially those containing pointers to other structs) can be a headache. But that can be overcome.

BTW, just FYI - C'ville is rapidly becoming very much like Marietta in terms of the traffic.