>Interesting side-note: the Abry patch is mention in this month's Advisor with this note: "Be aware this solution patches the FoxPro executable and may violate your license, warranty, or support contract with Microsoft."

Uh, well, maybe?

Unless you resell the foxpro executable, I doubt there is a problem. In any event, how is MS to know unless you tell it?

If the MS license requires that the foxpro executable remain unaltered, I doubt it's enforceable (if only on public policy grounds -- since modifying your own executable does not harm MS in any way), not to mention that if its broken and MS does not fix it, you have every right to fix it yourself. If MS actually did bring an action in this regard, the resulting public relations disaster would bring far more damage to MS that it could hope to repair by preventing customers from fixing their problems with MS products.

I have heard from several folks at MS that it is NOT going to revise 2.x in any way, so I strongly doubt the rumours that the remaining problems in 2.6 are going to be fixed by MS. Obviously, then, they will have to be fixed by others since they certainly need to be fixed.

regards,