>>
>>The difference I see is COBOL was developed by not by a software vendor but by the user community. There is a formal standard for COBOL that is largely driven by the user community, not the software vendor. If you don't want to be whipsawed by a software vendor then choose something like COBOL, JAVA, Python, etc. and accept the compromises you just bought in to.
>
>Actually, there is a formal, standardized COBOL, not from the community, but from a standards organization. The efforts to standardize xBase fell flat several years ago.
>
>>
>>Personally, I'm keeping my eye on Python; especially since I see it works with IBM's AS400 (oops, now the "iSeries"), along with Linux, Unix, Windows, MAC, and more.
>>
>
>Don't forget Microsoft's IronPython implementation.

Craig;

As I recall the IEEE (I was a member) suggested creating standards for dBase, and was sued by – you guessed it – Ashton-Tate. The xBase usage came into use but Ashton-Tate sued those parties using that term also.

Enter Borland – they purchase Ashton-Tate, and interest in dBase standards diminishes, along with all Ashton-Tate lawsuits being dropped (a blessing to the industry). Who needs dBase when you have “The Fox”? :)

Tom