Re: VB5.0 to VB6.0, And Access2000 Compability
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Sat, 19 Nov 2005 17:13:17 -0500
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:mJKdncRomp__-OLenZ2dnUVZ_tCdnZ2d@xxxxxxxxxxxxxxx
>
> "Mattews" <Mattews@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:EE793E7C-9555-409A-853C-88AA19995A8B@xxxxxxxxxxxxxxxx
>> I have a project about 90% done in VB 5.0
>> Im thinking about converting it to VB6.0
>> Is it worth the trouble? What advantages could I ger using 6.0 instead of
>> 5.0??
>
> I feel getting access to Replace() and Split() is well worth the time to
> upgrade.
>
> Besides all the wonders and glory that was VB5, VB6 is an upgrade and
> there
> are many subtle differences between it and VB5 as Bob eluded to. Why stay
> in
> the past.
Why? You can easily write your own functions to do what these functions do.
What is more important are features in VB6 not present in VB5 that you CAN'T
write your own functions to do. For example, returning arrays from a
function, Mateus, what you should do is check out the What's New page for
VB6 and determine for yourself if any of these features would be useful to
you:
http://msdn.microsoft.com/library/en-us/vbcon98/html/vbmscWhatsNewInVB98.asp)
If you think they would be useful, then upgrade. If you don't think you need
these new features, then don't bother upgrading. The other thing is though,
sometimes you don't (or can't) realize how useful a feature is until you've
actually used it. <g>
If Mateus can get VB6 for a very cheap price, then it's probably worth
upgrading to. But, it's not going to enable him to do anything that can't
be done with VB5.
>> And I want to use Access2000 for my database, so is it comaptible with
>> VB5.0? Will it be better if I use Access2000 with VB6.0??
> As Bob pointed out MSAccess has no impact.
Actually, it could. VB5 does not provide native support for Access 2000
databases. VB6 does IF the proper service pack for it is installed (I think
at minimum it needs to be SP4). This mostly has to due with the intrinsic
Data Control, which is hard-coded to use Jet 3.5x (and Access 2000 requires
Jet 4.0). This can be worked-around in a number of ways, though. Since
Mateus didn't mention what data access library he's using (DAO or ADO) or
whether he's using the Data Control, it's hard to say. It's *possible"
there's no impact, but you can't say that it's a certainty. A more correct
way of putting it would be: as long as you're using DAO 3.6 or ADO with the
Jet 4.0 OLEDB Provider and NOT using the Data Control or data binding, VB5
will work fine with an Access 2000 database.
Just for reference:
PRB: Error "Unrecognized Database Format" When You Upgrade to Access 2000 or
2002
http://support.microsoft.com/kb/q238401/
--
Mike
Microsoft MVP Visual Basic
.
- Follow-Ups:
- Re: VB5.0 to VB6.0, And Access2000 Compability
- From: Ralph
- Re: VB5.0 to VB6.0, And Access2000 Compability
- References:
- Re: VB5.0 to VB6.0, And Access2000 Compability
- From: Ralph
- Re: VB5.0 to VB6.0, And Access2000 Compability
- Prev by Date: Re: Early-bound
- Next by Date: Re: Directory Folder question
- Previous by thread: Re: VB5.0 to VB6.0, And Access2000 Compability
- Next by thread: Re: VB5.0 to VB6.0, And Access2000 Compability
- Index(es):
Relevant Pages
|
