>>>Anyone try VFP9 on the new Windows 10 technical preview yet? I downloaded the W10 ISO file but haven't got around to installing it yet.
>>
>>VFP9 will continue to work on any Intel base Windows version, until 128 bit or 256 bit processors comes around, which isn't likely to very happen soon.
>
>More accurately, VFP9 will continue to work on any Intel-based Windows version that supports Win32 and SMB networking. That said, VFP does some unusual things; if in future those are not adequately supported in a future Win32 implementation, that could de facto "break" VFP9 even if other Win32 apps run properly.
>
>That's why it's important to keep testing VFP9 on new versions of Windows.
>
>For example, a couple of weeks ago a long-time client started virtualizing its myriad physical servers. I was given a Server 2012 R2 VM to replace the old AMD K6-based NT4 workstation I was using on-site.
>
>I duly installed VFP5, 7, and 9. My first maintenance task was to make a table structure change. Did it in VFP5, hit OK, then confirmed "Yes, make changes permanent". That final action crashed the VM. Completely reproducible, did it several more times with VFP5, and a couple of times with VFP7 for good measure.
>
>Since that VM is also hosting production VFP tables a lot of other users were getting annoyed so I haven't had much chance to debug this yet.
>
>A Server 2012 R2 VM on vSphere should be rock solid, so it's a little disturbing I can crash one at will with a simple interactive VFP maintenance task.

If you ever follow up on this, pls. post. Running old say/get forms in a VM and switching remote user is does not redraw everytihing, minor PITA...