DWUTKA at marlow.com
DWUTKA at marlow.com
Fri Sep 22 13:37:29 CDT 2006
Most of my apps are web based. I use VB .dll's with ASP based front ends....don't have a lot of use for .Net forms... thanks for the link though. Drew -----Original Message----- From: Bobby Heid [mailto:bheid at appdevgrp.com] Sent: Friday, September 22, 2006 1:32 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] [SPAM SUSPECT] Re: Switching to VB.net Drew, If you are interested in extending any of those programs with .Net, you might be interested in this: http://www.microsoft.com/downloads/details.aspx?FamilyID=98c38c1d-c630-4d9a- 8bb5-7f1fc088a7c4&DisplayLang=en Microsoft InteropForms Toolkit 1.0 "This toolkit helps you bring the power of .NET to your existing VB6 applications, by allowing them to display .NET WinForms from within the same application. Instead of upgrading the entire code base, these applications can now be extended one form at a time. The goal is a phased upgrade, with production releases at the end of each iteration containing both VB6 and VB.NET forms running in the same VB6 .exe process." Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com Sent: Friday, September 22, 2006 1:47 PM To: accessd at databaseadvisors.com Subject: [SPAM SUSPECT] Re: [AccessD] Switching to VB.net Importance: Low I've used .Net, but not for any live systems. With the exception of inheritance, there is little I can't do in VB. A major obstacle is that I have so many systems built with VB, that developing new systems takes less time due to the amount of code I have built over the years. Drew -----Original Message----- From: William Hindman [mailto:wdhindman at dejpolsystems.com] Sent: Friday, September 22, 2006 9:53 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Switching to VB.net ...n-tier is just doublespeak for what you already do :) ...think of forms & reports as one tier ...the be mdb as another ...the code modules/classes as another ...Access puts them all together to avoid confusing the office user who works with it ...higher lever dbs don't need to make that compromise so they separate them ...it has its advantages ...and disadvantages. ...but so does Access ...I'm soooooo not switching ...MS may drag me to .net eventually but I'll be kicking and screaming and clawing at the floor the whole way :). William Hindman ----- Original Message ----- From: "Dan Waters" <dwaters at usinternet.com> To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Sent: Friday, September 22, 2006 7:52 AM Subject: Re: [AccessD] Switching to VB.net > Hi Charlotte, > > Thanks for this write-up! Turns out I do have the O'Reilly book. I > bought > it to try to learn and see if, for me, it's the right thing to do. > > I'll have to look up to see what n-tiered design is. If I don't need it, > then you just saved me a huge amount of time! > > Thanks, > Dan Waters > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust > Sent: Tuesday, September 19, 2006 6:41 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Switching to VB.net > > The hills are alive with references. One that still amuses me is the > O'Reilly book, "Visual Basic 2005 in a Nutshell", which totals 746 pages > and is 1.5 inches thick! That's one heck of a big nutshell! > > Rick Dobson's book, Programming Visual Basic .Net for Access Databases", > at least starts from familiar territory. There are also some good books > in the Microsoft .Net Development Series, including "Data Binding with > Windows Forms 2.0" and "Windows Forms 2.0 Programming". Be prepared to > be confused at first. If you don't understand classes, you'd better > learn fast because *everything* in .Net is a class, even a string is a > class instance. And if you haven't worked with ADO, you might as well > bite the bullet and get ready for ADO.Net. I found it much easier to > move to ADO.Net having worked extensively with ADO in addition to DAO. > You'll become familiar with XML whether you want to or not because > that's where you store stuff that used to go into the registry in Access > apps. That means you have to learn to read and write it using the > appropriate tools from .Net. > > The most difficult part of .Net is that you can do so much, in so many > possible ways, that you wander around in confusion looking for someone > to lead you out of the wilderness. I think this is one language where > some training is essential, although finding the right level of training > can be a chore too. The AppDev series on .Net is pretty good and takes > you through the basics quite well. Rick Dobson's books are good but I > haven't been at all impressed with him dvds, which strike me as > extremely home-made. Rick is a nice guy and he knows his topic but the > videos tend to wander. > > You'll probably eventually wind up using 3rd party controls, although > Microsoft is trying to cover those bases more with every release. The > next framework is slated to have a new UI in place of Microsoft Forms > (or maybe above or below MS Forms, I haven't figured that out yet) and > some nifty developer tools. If you want to do effective database design > in .Net, you have to learn not only relational theory but also n-tiered > design, since it's pretty pointless to build a .Net app in only one or > two tiers. > > All in all, it's a wild ride, but fun! > > Charlotte > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters > Sent: Tuesday, September 19, 2006 2:07 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Switching to VB.net > > Or - if you could point to a reference? (no pun intended!) > > Thanks! > Dan Waters > > -----Original Message----- > Subject: Re: [AccessD] Switching to VB.net > > Ye Gads! The best way is to get a good team leader who knows the thing! > I'm the veriest novice, but it's my bread and butter. Let me give it > some thought. > > Charlotte > > -----Original Message----- > Subject: Re: [AccessD] Switching to VB.net > > OK Charlotte! > > Since you have admitted switching to VB.net and are extolling the > virtues of said product, I want to ask you to do something! > > For those of us who are 'switching lurkers', we could use a write up on > how to go about this Big Switch! > > Any possibility? > > Dan Waters > > -----Original Message----- > Subject: Re: [AccessD] pretty quiet out there > > Naw, it's just that we're all switching to VB.Net and don't want to > admit it. LOL > > Charlotte -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com