I know Access 2007 will continu to support VBA, but for new applications I would like to use a .NET based solution. VSTA and VSTO come to mind, but VSTA is currently only available in Infopath 2007 beta, and VSTO v3 only gives you the ability to create application-level add-ins for Access.
Will VSTA or VSTO document-level integration be available for Access 2007, and which one would be the best replacement for VBA in Acces-applications
Replacement for VBA
Hot Topic
- VBA code to search and modify in Word
- API Used in VBA
- Find Method - enter value on one worksheet and search in another
- Using VBA macro to locate next free column on worksheet
- Excel Pivot Tables - Dynamically Changing Pivot Table Structure
- Office 10 \ winword.exe runtime error
- Change a value for a link to another Excel file
- VBA Module to DLL
- VBA for Powerpoint
- problem with mshflxgd.ocx in VBA
Replacement for VBA
Justin Patterson
<<I know Access 2007 will continu to support VBA, but for new
applications I would like to use a .NET based solution. VSTA and VSTO
come to mind, but VSTA is currently only available in Infopath 2007
beta, and VSTO v3 only gives you the ability to create application-level
add-ins for Access.
Will VSTA or VSTO document-level integration be available for Access
2007, and which one would be the best replacement for VBA in
Acces-applications >>
None of the above. If you want to go to a .NET solution, I outlined the
options open to you in my reply today, in a newsgroup.
It actually doesn't make any sense to use VSTO because, for a database
application, it should be simple enough to create a WinForm application
front-end to the database, using ADO.NET. Unlike other Office
applications, you don't need to be in the application to allow users to
work with the data. If you want .NET support, then you supposedly want
to use the capabilities the .NET Framework provides: securty, WinForms
controls, etc.
-- Cindy Meister