>It does boggle the mind why they are sticking with Fox. Looking at it objectively, it is a hard business decision to justify given the shallow pool of talent they have to choose from and that the pool will get more and more shallow.
>
>Seriously..there is no technical or business reason why they could not go with .NET... My guess is that there is one main person, he/she knows - or at least is acquainted with Fox - and in lock-step fashion - is what they are going to go with.

Well, if they were planning a full rewrite, it makes a decision like that a lot easier to make. However, I would guess they've got a large amount of legacy FP/VFP code that they're running their business on that will still need to be maintained/enhanced as they try to move forward. (From what I've seen), it's a lot easier dealing with V/FP data in VFP than from .NET. As they progress and start to move and/or push their data into SQL server, it becomes a much easier proposition to interact with that data from .NET (w/o requiring lots of interop code). Since .NET experience is listed as a plus, maybe they're thinking along those lines?