So I guess what we really need is a list of those limitations that were engineered into the software with the intention of preventing us from working around them and those that were not.

Unfortunately, that is the whole problem with the EULA. Microsoft's intent. Since they refuse to categorically state their intent, and insist on continually obfuscating their intent with weasel words, we are left wallowing.

Oh, well. If they want me, they can come and get me. I will surrender peaceably.

>There is another component with the 2GB limit for example. That is intent and what was practically "do-able" when that part was designed way back when. That one was a physical limitation, and the intent was NOT to prevent developers from using external databases to overcome that limit. MS has also explicitly stated that VFP has been designed to work and play well with SQL Server, Oracle, .Net (to some extent), etc.
>
>So, we also have to take the EULA into historical perspective with respect to other claims and statements MS has made in the past.
>
>>Absolutely. That's what I said originally. If it's abug, it's ok to work around it, if it's by design, it's not ok. Nothing to do with hacking the software code. Now, let's think again about that 2 gig file size limit.... ;)