>Cindy:
>One more thing - here in a conservative environment (NT4 and Office97) I think .NET will be slow to catch on because of the percieved security issues and other unknowns. That makes the choices for new development either VFP or VB6. Since VB6 is not forward-compatible in the way VFP7 is, VFP has a distinct advantage.
>JVP:
>When you say forward-compatible, do you mean web services? Be careful here!! VFP, in all material respects, has no more web service functionality than VB 6. As far as your security that is well taken as that is always a concern. As far as VFP being more forward-compatible than VB 6, I totally disagree with that conclusion.
>
>Could you expand more on your "forward-compatible" premise???

I'm not sure why you brought web services into the discussion.

Take 100 random VB6 apps and try to run them in VB7 without any conversion, or even with the built in converter (but no other programming.) Do the same with 100 random VFP6 apps running in VFP7.

As far as I know the VFP6 apps will generally run in VFP7, though there have been a few bug fixes which change a few things.

As far as I know the VB6 apps will not run in VB7, either unconverted or with the automatic converter. As far as I know the automatic converter converts most of the app and gives you a fix list of things you need to fix.

That's what I meant when I used the term "forward compatible."