Um.. gang? let me tell you a little story...
A long time ago in a galaxy far, far away, there was an accounting package called "Flexware". It was originally written in UCSD Pascal, ported in Pascal to the Mac, and it did quite well for itself. Someone decided that it really needed to be re-engineered from the ground up - in C. It took over a year, and it almost put them out of business, in order to convert to C. They gained no functionality, it cost them a fortune, and it almost put them out of business.
Believe it or not, there are a lot of people running code written in the 1970's in COBOL because the cost of re-writing this with more modern tools far exceeds the cost of maintaining the existing code base.
I think it would be foolish for Jon to convert Amazing Charts - which currently works under VB6 JUST FINE, to .NET **JUST** for the sake of converting to .NET. I agree that VB6 is a platform that borders on brain-dead in a lot of ways - no argument there. Even so, it's possible to use a perfectly good modern database under VB6 just fine, and conversion to .NET isn't a trivial hack. The decision to go to a different database engine should be totally separate from any decision to change development tools or platforms, and each decision weighed carefully for cost and benefit.
Regards,
V.
