Dan Waters
dwaters at usinternet.com
Tue Feb 21 13:22:00 CST 2006
OK Charlotte, What are these goodies? And the big question - what does it take to do the conversion (software, learning curve time, how to make reports, convert forms vs. modules vs. reports, etc.) For an Access application that has ~50K lines of code, is it worth it? Thanks! Dan -----Original Message----- That "juicy VBA goodness" can't hold a candle to the .Net goodies, Ken. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ken Ismert Sent: Monday, February 20, 2006 2:00 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] FYI: Good news - VBA in Office 12 and beyond... In fact, if you look at Visual Studio 2005 Tools for Office, you'll find it has no built-in support for Access yet... http://msdn.microsoft.com/office/understanding/vsto/default.aspx As usual, Access lags behind its Office companions in terms of the latest development platform support. That means we'll be able to hang onto that juicy VBA goodness for at least one release beyond any of the other Office components. :) -Ken -----Original Message----- From: Shamil Salakhetdinov [mailto:shamil at users.mns.ru] Sent: Sunday, February 19, 2006 7:24 AM To: !DBA-MAIN Subject: [AccessD] FYI: Good news - VBA in Office 12 and beyond... http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=190669&SiteID=1 Shamil -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com