>>Any reasons I shouldn't? Any issues I need to know about?
>
>Issues? Its a pretty demanding peice of software, so I hope you got the resources. And its beta software, so if you're at all hesitant betas, keep it in mind. Also, isntalling VFP7 installed the whole .NET SDK plus a Windows Upgrade. IE5.5 and Outlook Express are installed, and the XML Parser is updated. If you've got Windows 2000 it loads SP1. I suppose if you have NT is loads SP92 or whatever thats at.
>

No, SP 666.

>I installed the whole beta, and it really screwed over my machine, either that or reinstalling MSXML3 did. I'm doing some tests now to find out what happneed.
>

The XML actually implements two parsewrs - XMLDOM and SAX.

>In any case, I've been using VFP7 since only November and am already finding LBIS hard (Life Before Intelli-Sense :-) So I say if you've got a non-production machine thats pretty buff go for it!
>

You can add IntellisenseX to VFP6 - not quite as full-featured as VFP7's but it does work. Christof Lange posted it. And there's always CEE.

>I have the VFP7 tech preview on my work machine (its 95 so I can't install .NET if I wanted to) and VS6 too, no problems yet. But I just reloaded my home/mh.com-server 2000 machine and am only going to put VS.NET on it this time.

Coward. Real men install the Whistler beta that came in the January MSDN release (arrived at the door yesterday.) Along with all the other tech betas.