>
You did not address the issue I raised in my reply to Rod. What is the current "sustainable and contemporary platform"? Is it VB and Access?
Access seems to have better tools for building queries than VFP's View Designer. Is that the primary reason to use it as a data store. Isn't Access data as susceptible to corruption as DBF files?
>

Mike,

It does not matter what the "current sustainable and contempory platform" is. All that matters is that as far as this company is concerned, VFP is not it. Ask 10 companies for an opinion and you are likely to get 10 different answers. Some will say .NET/Windows, some will say Java/Linux, or some variant thereof.

I do not mean to imply that Aon in this case is using sound methods. Most I/T decisions, to one degree or another, are flawed. The issue Mike has to do with perception, not reality. It reminds me of all the OO chest thumping that was going on in the VFP world with regard to the lack of respect the tool garnered. All the while, many people in the VFP world could not understand how companies could adopt and embrace VB over VFP - given the fact that VFP supported implementation inheritence. The answer is simple...the rest of the world did not care. The perception was that VB was the supported tool.

It gets no more difficult than that...