Longtime "Lurker" who is HEAVILY in debt to your collectivecontributions!New Management is re-evaluating my first VBA Application and isconcerned it has reached, or is quickly reaching a limit. They (and theVB Consultant) have good points and are "re-thinking" the original Excelmandated solution.Has anyone gone through the perceived PAIN of porting VBA code to VisualStudio for Office Applications?If not yet, is anyone else researching the possibility and would like todiscuss?
No Opinions, experiences FEARS or friendly warnings?
Yes, and it was, is, painful.What do they mean by reaching a limit (is the VBA consultant reallyqualified to judge). I have projects with in excess of 25,000 lines ofcode in daily use, and they stand up fine.
Do I understand correctly that VSTO requires a full Setup.EXE(or WEB server) in order to deliver a VB modified Excel File?The problem is what we are doing with the data - GRAPHICALLY. Ihave taken the database info that was gathered via Forms and created aworksheet where each cell represents a 1" Grid to scale (50' x 16').AutoShapes, polylines and connector OLEObjects are then placed on thesheet. So far so good....Where the ceiling comes in sight is allowing the objects to bemoved (and tracked to scale), dragging with attached connectors, editingof the database criteria and enforcing business rules on that criteriavia events when an Object is edited.What started as a text based Configurator has evolved into avector graphic application.
VSTO requires a full install, Net framework et al, and you need XL2003at least.Are those constraints within VB or are they Excel, because if it isExcel, VSTO won't make any difference.
One of my plans would be to use the existing Excel with VBA file (xmloutput) as the database INPUT to a new Windows Forms application. TheMetaDraw ocx control would give me everything I could dream ofgraphically speaking but I will have to learn VB.NET.