Here's how I see this. There are many problems with this thread. I'm curious by nature so when I see something that could be interesting I read it. I guess that it's not like that for everybody on the UT.

BUT I think that another thread should be started in the VFP section. This should'nt be only in the "VFP and .net section" And with another title. It's all about marketing. A title like that will get VFP developers to read it and something should be created in the news section. If this is as good as it looks there should be a big announcement about it.

I'm also surprise that this thread did'nt see more action. Hmm could it be only because of the title? or the section?

>I'm hoping that it is simply that this is below the radar and others will see this thread and take a closer look. If this all works (and it appears that it indeed does so far) it is truly something worth diving into.
>
>I REALLY would like to see MSFT's take on this. Did someone make a blanket statement that it couldn't or shouldn't be done and everyone took that statement as written in stone? Did this group of guys just stumble onto something? I find the latter more difficult to believe and think that they deserve kudos for getting to a point that MSFT implied was mpossible or not worth pursuing.
>
>Perhaps the subject line of this thread doesn't accurately reflect the possibilities...
>
>Shouldn't someone be shouting this from the rooftops by now?
>
>
>
>>>>>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.
>>
>>With today's prices, many people can't afford to pay that much attention. Or this just went below the radar.