VB6 s/w to keep track in tournament
in [Visual Basic]
|
Prev: VSM 05/2002 Dan Fergus Article - Getting Debug Info from Production Apps
Next: Use Internet to network to VB5 app?
From: Tony Toews on 22 Jun 2010 23:45 On Tue, 22 Jun 2010 23:10:42 -0400, "Kevin Provance" <k(a)p.c> wrote: >You're only here because of the VBA >part of it (or so I am gathering). Not quite. I'm working on a VB6 utility which is up to about 12K lines of code. Mind you at least 3K of that is imported API calls and a few user controls. >He, like you dismissed VB away with a >single hand...so I'm not surprised at the loyalty factor involved. Whoa, I'm not at all dismissing VB6. I quite like it. I was just suggesting an alternative. Tony
From: Tony Toews on 22 Jun 2010 23:48 On Tue, 22 Jun 2010 22:09:39 -0400, "MikeD" <nobody(a)nowhere.edu> wrote: >My initial reply to you (in which I said I thought using Access was a >terrible suggestion), which kinda started this, was based on Saga saying "a >VB6 app", that Saga has been around on the VB6 newsgroups for awhile Obviously I'm not a long term person in the VB6 newsgroups. Furthermore I seldom even notice names when I'm posting a reply. Indeed, back in Fidonet days, I once got a netmail (equivalent to an email which was quite rare those days.) from someone who started with "Hi cuz, I saw your posting in the Access [Fidonet] echo..." I was thinking "What jerk is calling me cousin when I looked at his name again. Sure enough he was a cousin. (My excuse is that most of my cousins have a Mennonite last name so I might've noticed such a last name.) Tony
From: MM on 23 Jun 2010 02:14 On Tue, 22 Jun 2010 19:38:35 -0600, Tony Toews <ttoews(a)telusplanet.net> wrote: >On Tue, 22 Jun 2010 07:19:51 +0100, MM <kylix_is(a)yahoo.co.uk> wrote: > >>Boy, was I wrong! Access is, if you're a VB programmer, a pile, a >>veritable PILE of donkey poo. The UI is a royal PITA (compared to VB). >>Nothing in the Access UI seems to function like you'd expect it to, >>from the awful "switchboard" > >The MS supplied switchboard? That sucks. I never use it. Instead I >use command buttons on unbound forms. > >>to the way that properties are presented non-alphabetically. > >So what. On the property sheet they are grouped reasonably well both >in the individual tabs and in the All tab. I guess it's what you're >used to. > >>Access can be your friend! But I wouldn't wish its application UI on >>my worst enemy. > >I must say that this is one of the more eloquent and interestnig rants >I've read in quite a while. Well done. (And I don't mean this >sarcasticaly.) > >Tony (still chuckling) I've had a lot of practice! MM
From: Paul Clement on 23 Jun 2010 08:48 On Tue, 22 Jun 2010 22:09:39 -0400, "MikeD" <nobody(a)nowhere.edu> wrote: � > I must say that this is one of the more eloquent and interestnig rants � > I've read in quite a while. Well done. (And I don't mean this � > sarcasticaly.) � > � > Tony (still chuckling) � � Tony, the thing you gotta understand, and which you even mentioned elsewhere � in this thread, is a person's background. Now here, in in this specific � newsgroup, MOST people are going to have a VB6 background. Therefore, we're � partial to VB6. You, on the other hand, have an Access background, so � naturally you're partial to Access. However, most of us VB6ers would never � use Access for anything more than serving as the backend database for a � local database app (a movie, music database, for example...or another way to � put it, a "home" application). � � My initial reply to you (in which I said I thought using Access was a � terrible suggestion), which kinda started this, was based on Saga saying "a � VB6 app", that Saga has been around on the VB6 newsgroups for awhile and to � my recollection has never even mentioned development in Access, and that he � posted to a VB6 newsgroup and NOT an Access newsgroup (he probably would � have posted to an Access ng if he wanted to use Access). Taking all this � into consideration, plus a few more things, my opinion was that your � suggestion to use Access was not a good one. I didn't mean to start this � debate though. Access has some key advantages when it comes to building a database app. First, the data binding implementation is more capable and flexible than the data bound controls in Visual Basic and as a result you can develop database centered applications more quickly. Access also allows you to treat ODBC data sources as native (linked) tables so it's easier work with databases heterogeneously. A key advantage when building stored queries (QueryDefs) is that in Access you can call user-written VBA functions from SQL. Unfortunately, this is not supported via DAO, RDO or ADO. Of course there is other native functionality that Visual Basic does not have direct access to. My key issue with Access has been trying to work with the Forms within the Access application host. It doesn't offer near the flexibility as Visual Basic. Paul ~~~~ Microsoft MVP (Visual Basic)
From: Karl E. Peterson on 23 Jun 2010 14:12
Tony Toews formulated on Tuesday : > I must say that this is one of the more eloquent and interestnig rants > I've read in quite a while. Well done. (And I don't mean this > sarcasticaly.) > > Tony (still chuckling) Mike's been polishing his ranting style for at least a good decade now. Every now and then, it really shows. :-) -- ..NET: It's About Trust! http://vfred.mvps.org Customer Hatred Knows No Bounds at MSFT ClassicVB Users Regroup! comp.lang.basic.visual.misc Free usenet access at http://www.eternal-september.org |