Well, that's a thought. I do put all the windows on the second monitor, but I tile them so that I can see all of them at the same time. One thing I have noticed about docked windows is that they migrate. VFP does not seem to remember what order they were docked in, so if you like a certain order you're just out of luck. Are you running the code below at startup each time in order to force the order? Since the debugger runs in a separate window anyway, I haven't thought about putting it over on the second monitor. Thanks for the input.


>Run the code below, and then put the docked windows on your second monitor. I also have the debugger open on the second monitor as well. It works pretty well. It is personal preference, but with the docked windows I can click on the tab for whichever window I want to access and leave the rest of the screen real estate for the debugger and the entire first monitor for the app or the dev window. It's all personal preference but I prefer to use the 2nd monitor for all of the extra windows.
>
>

>   ACTIVATE WINDOW View
>   ACTIVATE WINDOW Properties
>   ACTIVATE WINDOW Document
>   ACTIVATE WINDOW Command
>
>   DOCK WINDOW properties POSITION 4 WINDOW view
>   DOCK WINDOW document POSITION 4 WINDOW view
>   DOCK WINDOW document POSITION 4 WINDOW view
>   DOCK WINDOW Command POSITION 4 WINDOW view
>
>   IF WEXIST('standard')
>      HIDE WINDOW standard
>   ENDIF
>   IF WEXIST('standard')
>      ACTIVATE WINDOW standard
>   ENDIF
>

>
>>Now hold on there, Sergey. You told me "To appreciate VFP windows docking, try dual monitor setup", but at that time I didn't have a dual monitor setup. So now I do and I'm wondering why I would need to dock these windows in a dual monitor setup. I figured that maybe I'm missing something and now you won't tell me about docking in a dual monitor setup? Come on . . . are you holding out on me?
>>
>>>Whatever works for you.