Moving from VB 3.0 to VB 5.0

[Ernest]

I have a medium size VB 3.0 database app which must be moved to VB 5.0.
I also have VB 4.0 still in its box as well as VB 5.0.

Should I first install VB 4.0 32 bit and get the app working with the
new facilities, ie convert to Recordsets, implement OCX's ,etc. As
VB 4.0 is more backwards compatible, I see this as an easier way
to move forward.

When all remnants of the older VB 3.0 approach are removed, I would
then convert this to VB 5.0.

Is this approach nonsense? and should I convert from VB 3.0 direct
to VB 5.0?

Your comments please.

Ernest
--
ernest at Noel Systems, near Kingston-upon-Thames (UK)
(if replying by email, remove the * from address)

[Bill McCarty]

Ernest wrote:
>
> I have a medium size VB 3.0 database app which must be moved to VB 5.0.
> I also have VB 4.0 still in its box as well as VB 5.0.
>
> Should I first install VB 4.0 32 bit and get the app working with the
> new facilities, ie convert to Recordsets, implement OCX's ,etc. As
> VB 4.0 is more backwards compatible, I see this as an easier way
> to move forward.
>
> When all remnants of the older VB 3.0 approach are removed, I would
> then convert this to VB 5.0.
>
> Is this approach nonsense? and should I convert from VB 3.0 direct
> to VB 5.0?
>
> Your comments please.
>

You can convert from VB3 to VB5. You do not need to go through VB4. If
you have some controls that are not in VB5 they will be come pic
controls. There are some OCXs that didn't make it VB5 but they are on
the CD. Also you can change from the 2.5 engine to the 3.5 engine. You
will need to make syntax changes but you can do this find\replace. Note
also you can keep the DB in Access 2.0 format if you want.

[Accufacts]

I tried converting an application from VB 3 to VB 4, but got stuck in that
I couldn't get VB 4.0 to read my workgroup database from Access 2.0
(system.mda). In VB 4, it wants the system database file to be
system.mdw. How do you get around that?

thanks

Scott Brown
Accufacts Screening, Inc.