Shamil Salakhetdinov
shamil at users.mns.ru
Tue Feb 21 16:06:33 CST 2006
> For an Access application that has ~50K lines of code, is it worth it? Dan, It all depends of course and it have to be carefully planned... Rough first estimation (I assume your code is rather clean and well tested): if you don't plan to rewrite DAO/ADO -> ADO.NET during conversion and if we assume that these 50K of code lines are not heavily MS Access object model bound - i.e. that these are more utility/data processing code then I'd say 50K code lines conversion VBA ->VB = 10 man/weeks (5 weeks code conversion, 5 weeks tests preparation, testing, deploying).... I did multiply "cowboy programmer estimate" of 4-5 weeks by two. It may need to be multiplied another two times to have 20 man/weeks, especially if you have a lot of code bound to MS Access forms specific forms and if you have a lot of complicated reports. One of my experiences of VBA (3 MS Excel add-ins) to VSTO based XL add-ins: - source code in three VBA addins: Sources ======= Files 74 (500KB) Pages 229 Words 47264 Chars (no spaces) 349,959 Chars (with spaces) 452,476 Paragraphs 11,840 Lines 14,621 Result ====== Files 76 (1MB) Pages 416 Words 88,454 Chars (no spaces) 803,394 Chars (with spaces) 1,066, 778 Paragraphs 18,123 Lines 26,460 The stats are collected by MS Word with all text merged into one file for source and for destination projects, font used 10pt Courrier new, page size A4. The result text size is bigger because during automatic conversion quite some comments are inserted, which I didn't delete all and because I did leave quite some converted code commented to see what was done etc. Conversion took one week work from scratch without in advance knowledge on how to write COM Add-ins using VSTO etc. There were several simple MS Forms forms only. During conversion DAO and ADO weren't converted to ADO.NET. Recap ===== If you/your company/customers are betting on .NET Framework(i.e. this is accepted long term goal and you have resources) then I'd not think long and just go (VS.NET 2005) - the more you will be programming on VB.NET/C# the more you feel yourself much more comfortable and safe than in VBA and after some (usally not long) start-up delay you will be quickly getting development time acceleration... Shamil ----- Original Message ----- From: "Dan Waters" <dwaters at usinternet.com> To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Sent: Tuesday, February 21, 2006 10:22 PM Subject: Re: [AccessD] Convert Access App to VB.Net (was FYI: Good news -VBA in Office 12 and beyond...) > 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 > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com