You are so right: I need to re-phrase the objective.

I'm trying to reproduce the funtionality of my Excel applications in
Visual Basic so the end user doesn't have to have Excel installed.

I presume this will mean using grids and generic objects instead of
workbooks/worksheets and mso objects.

In my fantasy, there is a tool that will allow me to map Excel-specific
references to VB.net (or even VB6) equivalencies, and preserve most of
the code.

If there is not a tool, perhaps there is a document that
cross-references VBA to VB.net. (If there isn't one, there should
be...I may have to make one someday.)

Some of the applications include a lot of graphics for simulation. It
was pretty easy to put them on a grid in Excel, but I presume I can get
better and faster results in a standalone VN.net application. I just
dread spending 6 months doing the re-writes.

Thanks for your help.

Mike Burke


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!