>>I have a choice - devote time to VFP which has seen far more days than it has ahead of it or devote time to VS .NET - which I think has a promising future.

Why not use both? I'm doing so by substituting VFP for ADO.NET. This way I can use VFP for data intensive Web Services and VS.NET for everything else. I'm working on a project right now using this framework and really feel I'm leveraging the best of both products.

Charlie