>Steve,
>
>Maybe the following will help folks understand exactly what the Foxteam faces.
>
>First, there have been a bunch of functions in Win2K that have superceded existing ones, which remain for backwards compatiability. In fact, this is not only the case with Win2K, but exists for for versions as close as Win95 OSR1 and OSR2. As an example, consider that the DISKSPACE() function caps the available space at 2gb. Why? Because the function it calls (GetDiskFreeSpace()) does. The function that retrieves the correct value (GetDiskFreeSpaceEx()) didn't come into being until Win95 OSR2. So the team has to code for the different versions of the OS, and decide what to return under OSR1 in this case.
>
>Second, and really a bigger issue has to do with the way VFP interally makes its calculations. For example, while we don't normally think of data typing in variables too much VFP does. Consider that the bitwise functions always return signed 32 bit integers. Do the following:

lnvar = 0xFFFFFFFF
>? lnvar && 4294967295
>lnvar = BITOR(lnvar, 0)
>? lnvar && -1

So the team has to determine the size of the integer it's going to deal with 32 or 64 bit, signed or unsigned.
>
>This isn't even the tip of the iceberg.

George,

So, are you saying that we are not as close as we think? < bg > I know that the work on MS part is not trivial for MS. I'm only pointing out that the tough work lies on MS. Further, many issues like this are OS issues, and would exist even if VFP remained 32-bit.