>>Hi Thomas:
>>
>>Are you a wizard? :-) You are actually right, the 32 bits limits is related to the usual function used for Locking and Seek. But in Linux and Windows there are counterparts of these functions with 64 bits. So what happens when you rise the limit to 64 bits?, you get exabytes.
>>
>>Best Regards,
>>
>>Samuel David
>>eTecnologia.net
>
>Now you guys are the greatest mystery of the day.
>
>Makes me wonder... if at the time of VFP7 we were forced to decide "in VStudio or out of it", i.e. "dot net XOR VFP as we know it", it was presented as "VFP would have to lose its native data engine etc etc". It was a big, 28-pixel XOR for the last five years at least, just like the story that "crossing the 2GIG boundary would require a major rewrite of VFP's core"... now if you guys, slightly less rich and probably a few megabytes shorter in other resources then Microsoft, managed to do that all (have both native VFP and CLR in the same compiler, and cross the 2Gig boundary), I have only one question: was Microsoft Fox team unable or forbidden to do the same thing?
>
>You've just shattered an illusion. Unbelievable. I thought software can't surprise me anymore.

I'm asking myself the same questions. Also, I expected to see 100 messages in this thread after the first hour, but we have 10 in 10 hours.