>>>>>I have a VFP5 app and am trying to use the multi-monitor capability in Win98. When I slide my program to the secondary monitor, the mouse does not work on the menu or any objects on the form. The mouse does work on the title bar (to max, min, and close), however. Also, keyboard shortcuts behave properly. Any suggestions would be greatly appreciated.
>>>>>
>>>>
>>>>This is an issue with VFP5; it doesn't know how to resolve the mouse location on secondary or tertiary monitors in the multi-monitor environment, so VFP-controlled form objects don't work as expected via the mouse. The standard windows control boxes are handled outside of VFP itself, so they work, and the keyboard commands don't rely on the cursor coordinate system, so they work as well.
>>>>
>>>>I don't know if this was resolved in VFP6.
>>>>
>>>>>thanx, David
>>>
>>>
>>>It works in VPF 6.0
>>
>>Thanks. Is there a method to determine which monitor the current VFP window is on, or do I need to grab the Win32 hWnd for the active window and use the API to figure it out? Also, if ypou happen to know, what do the mouse coordinate functions in VFP return when the cursor is on a secondary monitor?
>
>
>No functions to determine monitor. I don't know how to handle the mouse coordinates.

Not a problem. I can use the API to do it if I really need to worry about it.

Is the debugger well-behaved on a secondary monitor with the VFP app running on the primary? That would be invaluable from a developer's perspective; under VFP 5, I had problems, and even running at 1280x1024 (about the limit of what I can handle comfortably on a 19" monitor) I'd kill for more screen real estate. I've got a couple of retired PCI video boards that'd make nice secondary display cards, like a Matrox Millenium and a Mystique 220 card, which are well-supported as secondary cards under NT 4 with the Matrox G200 and the new G400 AGP cards.