VSTO vs. VBA

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

Can someone help me with information on using Visual Studio Tools for
Office vs using the Access VBA editor? I'm very familar with using the
VBA editor. My new job has given me access to VSTO and I'm considering
when to use it. Can you share your experience?

--For existing Access-based tools, can VSTO be used in place of the
VBA editor?

--How much upgrading is needed if I wanted to change from VBA to
Visual Basic?

--Is VSTO a better way to go for new Access-based applications?

--Generally... if VSTO worth the trouble?

Thanks!
 
Hi, Scott.
--For existing Access-based tools, can VSTO be used in place of the
VBA editor?
Click to expand...

No. However, one can write managed Add-ins with VSTO 2005 to work with
Access 2007 databases. It won't replace VBA just yet, though. Perhaps it
will with the next version of Access.
--How much upgrading is needed if I wanted to change from VBA to
Visual Basic?
Click to expand...

You'd have to change the entire front end, from Access to a VB.Net solution.
The general consensus is that it takes three to ten times longer to build a
VB.Net front end when compared to the Access front end.
--Is VSTO a better way to go for new Access-based applications?
No.

--Generally... if VSTO worth the trouble?
Click to expand...

For very specific application Add-ins for Access 2007, yes. However, for
general database application development in Access, SQL and VBA are still
the only programming tools.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Back
Top