Hi Andre --

Mind if I share a bit of history with you?

Would it really matter if I did?

VB7 might be to VB what VFP 3 was to Fox.

Then again, it might simply be a useful upgrade. <g>

It'll be the first release after a major re-engineering effort in the VB codebase to surface an object-oriented programming interface.

Ummmm, huh? You really didn't mean to sound quite as silly as that came across, right?

It's also the first release requiring drastic new mindset by hundres of thousands of VB developers, not to mention countless legacy applications and incalculable backward-compatibility issues.

Well, I know y'all had your share of difficulties in the past, but I really don't anticipate those for folks using VB in the future. Nothing like the transitions here.

If the history of VFP is anything to go by, there might be a huge risk in overselling VB7, in the sense that it may take several years for a fully object-oriented VB to become sufficiently stable and feature-full.

That's pretty funny, really. You've really not been paying attention over the last few years, have you? Ask JVP sometime whether this line of thought gets anyone anywhere productive.

So maybe VB7 will need to be taken with a grain of salt, needing a subsequent release or two to actually become usable in practice.

The odd numbered releases tend to be better. <g>

Later... Karl