>>In all seriousness, when considering the IT departments as a whole, I would imagine a majority would go for number 3. Developers who work under short deadlines will opt for #1 (or start sending out resumes) Our IT dept is still using NT 4.0 SP6, and has not ever considered upgrades to Win2k, and there is still another OS version on the horizon for release this fall. I have to agree with the thinking that "If it ain't broke, don't be fixing it." This means that if your applications run stable on WinNT, there is no reason to pump up Microsoft's coffers just to get the newest bundle of bugs.
>
>But what does NT vs. W2K have to do with upgrading to VFP 7?
>
>Tamar


Merely an analogy of going to the next level of technology just because it is there, and not yet determined a need for. and the differences of thinking between the net admins, and the application developers and software engineers. In a serious vein our network security people are already taking sides in opposition to the deployment of .NET technology and the compiler environment, and trying to build their case that it will compromise data and network security. As for me, I look forward to working with the release version of VFP 7.0. I am sure it will be a lot different from the Beta version I played with in VS.NET beta.