Re: Advice Needed...
- From: "Michael C" <nospam@xxxxxxxxxx>
- Date: Wed, 23 May 2007 09:44:07 +1000
"Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u2nV1cInHHA.3872@xxxxxxxxxxxxxxxxxxxxxxx
I don't need userdraw functionality in a listbox, so it's never been a
concern for me.
That is just one example though. I've used many API for controls over the
years.
As for what's better about them, I suppose it depends on what you're
trying to do. Certainly data binding's much easier in Access, though
that's to be expected. I think the biggest single thing that I find
useful in Access listboxes (though there are probably others if I go
looking) is that they can handle multi-column data, where a VB6 listbox
can't, AFAIK.
You can use a grid or listview in that case in VB. As for the databinding I
don't use it in VB so don't miss it. If that's the sort of thing you want to
do access is a lot better.
It does? I've never had a database prompt me to upgrade, unless it was
v2.0 or before...which is more than a little old at this point.
If you're using Access97 then it will ask to upgrade.
I suspect that comes back to what you're doing with it, and how you're
doing it. I've yet to see a VB6 app that I thought felt more professional
than an Access app (in fact, most that I've seen come across as dinky
little flunky apps...though I blame that entirely on their designers, not
VB6 itself).
Given equally qualified developers access will definately look less
professional. The controls and forms don't look like a standard windows app.
You can't get the forms to behave quite right in all cases. It's just not a
real app.
That said, I've seen a few that have come across as equal, and only rarely
one or two that I thought felt more professional, and those few were
because they were using snazzy outside controls and the like, that one
normally wouldn't think of in Access because their predecessors are
available and will get the job done...they just don't look/feel quite as
nice.
I'm not talking about the work done by the developer themselves. More the
work done by MS on each of the environments.
With a few problems, as I understand it. Certainly since the release of
Vista, I've seen a lot of posts here talking about problems getting either
VB6 itself or a VB6 app running on Vista.
The only one's i've seen have been due to vista permissions which is really
the fault of the developer eg writing to the prog files dir.
Which was sort of the point...migrate your apps to our new structure, or
continue to use the old one and just ignore the new one...but you can't
use your old stuff in our new stuff. (Or get bogged down in COM interop,
but that's a whole 'nother set of problems.)
That's true but both are still available.
Yeah, I can see it adding up in some cases, but I'm surprised that that
would really be that big of an issue.
For most VB stuff it wouldn't but that's because that's what we're used to.
C developers are used to being able to do stuff like modify video streams
with arrays at high speed.
Michael
.
- Follow-Ups:
- Re: Advice Needed...
- From: Robert Morley
- Re: Advice Needed...
- References:
- Advice Needed...
- From: jmar
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Bob Butler
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Robert Morley
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Robert Morley
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Robert Morley
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Robert Morley
- Re: Advice Needed...
- From: Michael C
- Re: Advice Needed...
- From: Robert Morley
- Advice Needed...
- Prev by Date: Re: Advice Needed...
- Next by Date: Re: Advice Needed...
- Previous by thread: Re: Advice Needed...
- Next by thread: Re: Advice Needed...
- Index(es):
Relevant Pages
|