Logo 
Search:

MS Office Forum

Ask Question   UnAnswered
Home » Forum » MS Office       RSS Feeds

Excel VBA application: Porting to Visual Studio 2005?

  Asked By: Abarrane    Date: Feb 11    Category: MS Office    Views: 1191
  

Longtime "Lurker" who is HEAVILY in debt to your collective
contributions!



New Management is re-evaluating my first VBA Application and is
concerned it has reached, or is quickly reaching a limit. They (and the
VB Consultant) have good points and are "re-thinking" the original Excel
mandated solution.



Has anyone gone through the perceived PAIN of porting VBA code to Visual
Studio for Office Applications?



If not yet, is anyone else researching the possibility and would like to
discuss?

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Hariz Burki     Answered On: Feb 11

No Opinions, experiences FEARS or friendly warnings?

 
Answer #2    Answered By: Bien Nguyen     Answered On: Feb 11

Yes, and it was, is, painful.

What do they mean by reaching a limit (is the VBA consultant really
qualified to judge). I have projects with in excess of 25,000 lines of
code in daily use, and they stand up fine.

 
Answer #3    Answered By: Freddie Evans     Answered On: Feb 11

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. I
have taken the database info that was gathered via Forms and created a
worksheet where each cell represents a 1" Grid to scale (50' x 16').
AutoShapes, polylines and connector OLEObjects are then placed on the
sheet. So far so good....

Where the ceiling comes in sight is allowing the objects to be
moved (and tracked to scale), dragging with attached connectors, editing
of the database criteria and enforcing business rules on that criteria
via events when an Object is edited.

What started as a text based Configurator has evolved into a
vector graphic application.

 
Answer #4    Answered By: Jonah Brown     Answered On: Feb 11

VSTO requires a full install, Net framework et al, and you need XL2003
at least.

Are those constraints within VB or are they Excel, because if it is
Excel, VSTO won't make any difference.

 
Answer #5    Answered By: Boyce Fischer     Answered On: Feb 11

One of my plans would be to use the existing Excel with VBA file (xml
output) as the database INPUT to a new Windows Forms application. The
MetaDraw ocx control would give me everything I could dream of
graphically speaking but I will have to learn VB.NET.

 
Didn't find what you were looking for? Find more on Excel VBA application: Porting to Visual Studio 2005? Or get search suggestion and latest updates.




Tagged: