>OK, but I don't see the Fox Team making use of any 64-bit extensions that would not be downward compatible with 32-bit Win, do you? I mean, it's not like the Good Old Days when you had FOXPRO and FOXPROX.

>But wouldn't it be cool if you could choose 32 or 64 bit compatibility for your apps at build time? And it would optimize and link accordingly? (HINT, HINT Calvin, Randy!!)

As I mentioned to Craig, it may very well be a product similar to VFP 3.0 that generated the compiled code based on the underlying OS. However, you do raise a good point regarding compatibility with Win32. However, keeping things compatible even within versions of Win9x can get a bit tricky. Some functions within some versions of Win32 aren't available in earlier versions.

One interesting side note is that Win32 does "understand" the concept of a 64 bit integer. The function GetDiskFreeSpaceEx() in the API utilizes them. If you look at my recent FAQ on a workaround to the SYS(2020)/DISKSPACE() bug on machines with either more than 2 gb free or total (depending on the function), I used strings to hold the return values. The reason being that while Win 95 OSR2 (at most) and above may recognize a 64 bit integer, VFP has no concept of them. So that's one thing, I think we'll see in the next version.