What if there was a NEW vb6

[dilettante]

I use agile development methods - I need to do 50% of the db, 50% of the UI - show the client - THEY ARE going to ask for CHANGES - do another 20% - show more - another 20% - never done - that's what maintenance is for!

Not sure how a VB6 design time database connection would make that any better (as Dil suggested all true VB6er's must do).

agile development:

Euphemism.

Repeatedly throwing code at the wall until it sort of sticks. When it slides off the wall again blame the user, then throw some more.

Bonus: though nothing ever gets completed and the product at any time is usually a Rube Goldberg Machine and is impossible to maintain... you can use semi-skilled coders and the cabal of involved users are supportive because they "got to be involved instead of doing my boring real job."

A win for those involved and a huge loss for the organization.

Sort of the Monty Python's Upper-Class Twit Olympics for programmers.