Folks,

I need some advice from the MVP's out there. I have a lot of Excel/VBA
applications that I have developed over the last 5 years. These
applications are for financial forecasting, consolidating financial
statements, sales and cost analysis, and derivative pricing models. Many
of these apps are really complicated (hundreds or even thousands of lines of
code) and most are still in use.

I presume that these apps will all have to be eventually converted to
Basic.net? And, since any major upgrade is going to come with a client
"wish list", that could be a lot of work.

So, do I start building new libraries and push the clients to convert now?
Is Version 12 is going to support VBA? If so, this may give me another 18
months of breathing room. What about new Excel projects? I would think
that I should use .net for all future projects. Assuming my code is fairly
structured and well commented, how difficult is it going to be to convert to
..net.

Any experience you experienced programmers could give me here will be
helpful.

Cheers,

Allan P. London, CPA