>George:
>
>Thanks for the reply. Good to know some other people are experiencing some of the same problems, and it's not just something I'm doing wrong. What has bothered me and bothers me still, is that it seems that VFP hides some the window configuration options as opposed to if you would have CWnd (?) object in C++.

Josh,

I don't think you're doing anything wrong. VFP just deals with some things differently than other applications. Messagaging for example.

One thing I've noticed is that VFP's windows seem to change class names with each version. Other MS products, don't. Word is one example, VB another. Why? I'm not sure why this would be. < Lesse, VB's forms are of the class Thunderform...mmm...maybe VFP's should be RunsLikeAFoxForm< bg > >They do, however. Additionally, top-level VFP forms are different in their very make-up from a top-level VB form, but an in screen VFP form is the same. Why? You got me.

>I'm not interested in the system tray icon. I conquered that area already. (That's where I had the form that when the sys tray icon was clicked, would unhide, but not get focus.) What I meant was I would like to mimic Microsoft's configuration windows that seem normal (have a titlebar) but no taskbar entry. Date/Time Adjustment and Display properties are examples of this.
>
>
OIC. Missed what you were getting at. We can do a little detective work here to find the answer. Before doing so, I would've guessed that either it was something in the window style property that did this or that it was the child window of another, invisible application. After checking it out, it seems, at least in the instance of the Date/Time dialog, that it's the latter. Its parent window is shown as RunDLL. This is where a tool like Spy++ is invaluable in uncovering these little mysteries.