Steve Erbach
erbachs at gmail.com
Tue Feb 21 19:36:45 CST 2006
Charlotte, Thank you very much. I have the Murach series of .NET books, two O'Reilly books on ASP.NET (the Cookbook and Programming With), three early Microsoft books on .NET, and a Wrox book on Crystal Reports. My Safari subscription has been very useful along those lines, too. On my bookshelf I've got the O'Reilly ADO.NET Cookbook, the Programming ASP.NET 3rd edition, and the Programming C# 4th edition. Are you talking about the .NET Power Suite for Visual Basic .NET or Visual C# .NET? I see that those are currently $2517 and $1437 without books. Hoo boy! I'll bet they were pretty thorough! I see a used copy of Rick Dobson's "Programming Microsoft SQL Server 2000 with Microsoft Visual Basic .NET" available on Amazon for $135.99!! Otherwise he has a lot of Access-based books. Don't see any others on .NET really except for one on SQL Server 2005 Express. F. Scott Barker appears to be the author of that 2002 book on ADO.NET and VB.NET. Thanks again. Steve Erbach Neenah, WI http://TheTownCrank.blogspot.com On 2/21/06, Charlotte Foust <cfoust at infostatsystems.com> wrote: > My employer purchased the .Net training series from AppDev and I went > through quite a bit of it. I also have a couple of Rick Dobsons books > on VB.Net and a very useful tutorial book, Database Programming with > Visual Basic.Net and ADO.Net. It is out of date and doesn't use Option > strict, so it is a good exercise to make the examples run anyhow in a > current and more restrictive environment. ;o> > > Charlotte > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach > Sent: Tuesday, February 21, 2006 2:05 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Convert Access App to VB.Net (was FYI: Good news > -VBAin Office 12 and beyond...) > > > Charlotte, > > Very good little summary of the features/benefits of using .NET. > > Could you tell me what resources you've used to support your learning > curve? That is, books, on-line code samples, hands-on courses, > magazines, web sites, etc. Do you have any "mentors"? People who you > think are tops when it comes to writing about .NET or coding in .NET? > > Thanks, > > Steve Erbach > Neenah, WI > http://TheTownCrank.blogspot.com > > > On 2/21/06, Charlotte Foust <cfoust at infostatsystems.com> wrote: > > I don't know where to start, Dan. It would be a total rewrite, but > > the program logic could be used to build the new app. Learning curve > > is steep because *everything* is an object and doing anything to it > > (like populating a string that already has text) creates a NEW object > > with the same name. You don't do things the same way, but it is much > > easier to get at and manipulate data, to create datasets that include > > related fields from another table, to create reusable code. The list > > is endless. ADO.Net is GREAT, and I *liked* ADO. Building forms and > > user controls is quite different from Access because you have so much > > control over the objects and their behavior. Reports can be used in > > our web-based app or on Windows without modifications. Do you want to > > > bind different parts of a form or report to different data sources? > > No problem. Do you want to bind controls to the top, left, right, > > bottom of the container so they move when the object resizes? No > > problem. Do you want a panel to fill its allocated space and stay > > that way through form resizes? No problem. Do you want custom > > behavior from a control? Create your own and use it in you apps. > > > > I'm a fan, as you can tell, but it is also easier to sell clients on > > .Net apps than on Access applications, justifiably or not. We build > > our apps so that we can connect to either an Access or SQL Server > > backend without changing any of the code, which makes it easy to > > switch a client over when they need the added capacity of SQL Server. > > > It takes planning and learning and effort, so don't do it unless you > > are willing to commit to those things and you are willing to use > > managed code. There is no point at all in building one-off code in > > .Net. That's a waste of time and energy. > > > > Charlotte Foust > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters > > Sent: Tuesday, February 21, 2006 11:22 AM > > To: 'Access Developers discussion and problem solving' > > 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 > -- > 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 > -- Regards, Steve Erbach Scientific Marketing Neenah, WI www.swerbach.com Security Page: www.swerbach.com/security