>>I experimented the same thing last summer and the only way I resolved this was to change the theme (in the display properties) from Windows XP to Windows Classic. It looks like the beta version of VFP 7 does not support the new XP interface.
>
>But just to clarify, VFP 7.0 (the shipping version) works great under Windows XP. I have used Windows XP for 3 months now, and I have yet to see any blue screen or lock-up yet, I've never had to re-boot once, and VFP 7.0 runs great on Windows XP. Windows XP is the most stable version of Windows ever released and makes a great development and deployment platform for VFP 7.0 applications. This thread disusses beta software running on beta software, so I'd thought I'd reply and clarify that those results have no reflection on the shipping versions of VFP 7.0 and Windows XP.

FWIW, I'll second that; I'm having great success developing VFP 7 on XP Pro; Compaq 1.1GHz Celeron, 384MB, dual flat panel monitors on a Matrox G550 is an absolute pleasure, and some of the features of XP are absolutely addictive - I especially like the ability to move a bunch of files to the CD-RW and let XP figure out how to handle the write to the CD-RW drive based on the type of media I've loaded makes life a no-brainer. VFP 7 is behaving wonderfully well on dual monitors; my only complaint is that some of the VFP Windows are anchored to the primary screen, but the debugger, property sheet, command window and class browser will happily sit on the secondary monitor while debugging a live app on the primary monitor. I have several clients running XP Pro on the eMachines T11090 (900MHz Celeron, 128MB RAM, Intel video chipset on board; I've had them all upgrade to at least 256MB (I'm paying about $20-25 for a 256MB PC133 168 pin SDRAM SODIMM); that's a $399 box, add about $20 for more RAM, about $15 for the NetGear FA311 10/100 EtherNet card, and about $125 foir a mediocre 17" monitor, and of course XP Pro - it ships with XP Home, acceptable in a peer-to-peer environment with few users, but far less than optimal in a domain environment. It's an easy sell, even to the cheapskates trying to squeak by on their delapidated Pentium 200 antiques...