I don't know if that's a valid counter-argument, Ed. You are certainly correct that VB and VC++ developers better understand threads, processes, and the sticky little nuances of dig-deep Windows coding. So they make superior components. Yeah? So? These same "Masters of COM" will design tables with no primary keys; wouldn't know RI if it bit them in the butt.

In fact, whats really telling, is that most VFP developers will profess to want to learn more about the nuances of Windows programming or the Web or other "to-the-metal" concepts, but a lot VB developers openly flaunt ignorance of databases and data design.

Database concept speakers at VBITS get ragged on big time.

Now, consider the full lifecycle needs in systems development: What's more important in both knowledge and attitude?

>They have to be to escape the brain-damaging crutches imposed by the language. A simple test - what percentage of VFP developers know what in the context of a process or a thread, the concept of a handle represents, as opposed to a token or an id? I'd venture to guess that the percentage is vanishingly small, especially when compared to people developing in C++ or Java. The typical VFP programmer isn't aware of what the differences are, and won't lift a finger to learn it unless jabbed repeatedly with a powerful cattleprod. The lack of initiative on the part of the VFP developer community creates the need for 'backwards compatibility'. How much hue and cry came from the BASIC developers when BASIC transiteds to VB, and gave up a whole lot of 'backwards compatibility' in the process.