Convert MSAccess2000/2002 -> VB6

[George Aslanis]

Hello,

Has anyone seen source code which will convert an MSAccess app to VB6?

Thanks,
George

 

[Douglas J. Steele]

Tony Toews lists a number of products at
http://www.granite.ab.ca/access/accesstovb.htm that purport to be able to do
this, but the general consensus is that they do an incomplete job at best.
There are simply too many differences between the controls available in
Access and those in VB.

You're probably better off redesigning your forms in VB from scratch. You
should, of course, be able to salvage much of your code: just copy it from
Access, and copy it into VB.

 

[Billy Yao [MSFT]]

Hi George,

Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this issue.

I think Doug has pointed out ways to convert Access to VB6 but you should be aware that the
structural and object model differences are sufficiently great that no product can convert a
"good Access database" to a "good VB application".

We have had reports that third-party converters are a significant assist in such a conversion,
but there is still a great deal of manual work to be done. So I agree with Doug that it's maybe
better to redesign the Access Objects in VB rather than convert them just using a tool.

If you'd really like to, you can try Greenwich Financial Modeling, Inc. at http://www.GFMinc.com
who has a program AccessToVB. Below are a few quotes from their Readme.txt you might
find helpful for you:

======================

AccessToVB requires the following files be installed and registered for proper functionality:

EITHER Microsoft Visual Basic 4.0 Professional or Enterprise Edition
OR Microsoft Visual Basic 5.0 Professional or Enterprise Edition
Microsoft Access 97
EITHER the Sheridan Data Widgets 2.0
OR the GreenTree DataList 1.0 OCX controls
OR the Sheridan Data Widgets 3.0

None of the above programs are included with Access97ToVB. If you are converting paged
forms or tabbed forms into a VB 5 project, you must have VB 5 Service Pack 2 or later.

If you have the Sheridan Data Widgets 2.0 controls, you must have at least version 2.0b (Build
186). If you have the GreenTree DataList controls, you must have version 1.0d or higher. At
the time of this writing, the current version of the Sheridan control is 2.0c (Build 198), and the
current version of the GreenTree control is 1.0h (build 39).

---------------------------------
Part 1 - About AccessToVB
----------------------------------

AccessToVB is the only product currently available designed to convert programs written in
Microsoft Access 97 to equivalent Microsoft Visual Basic 4.0 or Microsoft Visual Basic 5.0
programs. AccessToVB analyzes the database, and then converts the forms, macros,
modules, and code behind forms to Visual Basic.

There are a number of user selectable options, including which forms and modules to convert,
the choice of custom controls supported, and the ability to convert the project to an MDI
project. All standard Access controls are converted, including the new Tab control.

Unlike competing programs, AccessToVB also converts: secured databases, menus,
macros, toolbars, and paged forms. AccessToVB also converts multicolumn list boxes and
combo boxes, in both bound and Value List mode. Another serious shortcoming of competing
products is that the code is converted, but not translated. AccessToVB actually translates
Access syntax into Visual Basic sytax (Yes, Docmd.Openform "Employees", acDialog does
become Employees.show vbModal!)

If you have the evaluation version of AccessToVB, you may purchase the full version by
calling (212) 480-8217. The price is $395, plus shipping.
======================

Good Luck George! If there is anything more I can still do to assist you, please don't hesitate
to let me know. Thanks again for using MSDN Newsgroup!

Best regards,

Billy Yao
Microsoft Online Support

 

[Van T. Dinh]

.... and beware that the note mentioned VB4 or VB5 so the conversion software
is aimed at Access97 or earlier.

Since Access 2K uses VBA 6 (equivalent of stand-alone VB6), it is likely
that anything new in Access2K / VBA6 won't be converted correctly.

--
HTH
Van T. Dinh
MVP (Access)

Hi George,

Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this issue.

I think Doug has pointed out ways to convert Access to VB6 but you should be aware that the
structural and object model differences are sufficiently great that no product can convert a
"good Access database" to a "good VB application".

We have had reports that third-party converters are a significant assist in such a conversion,
but there is still a great deal of manual work to be done. So I agree with Doug that it's maybe
better to redesign the Access Objects in VB rather than convert them just using a tool.

If you'd really like to, you can try Greenwich Financial Modeling, Inc. at http://www.GFMinc.com
who has a program AccessToVB. Below are a few quotes from their Readme.txt you might
find helpful for you:

======================

AccessToVB requires the following files be installed and registered for proper functionality:

EITHER Microsoft Visual Basic 4.0 Professional or Enterprise Edition
OR Microsoft Visual Basic 5.0 Professional or Enterprise Edition
Microsoft Access 97
EITHER the Sheridan Data Widgets 2.0
OR the GreenTree DataList 1.0 OCX controls
OR the Sheridan Data Widgets 3.0

None of the above programs are included with Access97ToVB. If you are converting paged
forms or tabbed forms into a VB 5 project, you must have VB 5 Service Pack 2 or later.

If you have the Sheridan Data Widgets 2.0 controls, you must have at least version 2.0b (Build
186). If you have the GreenTree DataList controls, you must have version 1.0d or higher. At
the time of this writing, the current version of the Sheridan control is 2.0c (Build 198), and the
current version of the GreenTree control is 1.0h (build 39).

---------------------------------
Part 1 - About AccessToVB
----------------------------------

AccessToVB is the only product currently available designed to convert programs written in
Microsoft Access 97 to equivalent Microsoft Visual Basic 4.0 or Microsoft Visual Basic 5.0
programs. AccessToVB analyzes the database, and then converts the forms, macros,
modules, and code behind forms to Visual Basic.

There are a number of user selectable options, including which forms and modules to convert,
the choice of custom controls supported, and the ability to convert the project to an MDI
project. All standard Access controls are converted, including the new Tab control.

Unlike competing programs, AccessToVB also converts: secured databases, menus,
macros, toolbars, and paged forms. AccessToVB also converts multicolumn list boxes and
combo boxes, in both bound and Value List mode. Another serious shortcoming of competing
products is that the code is converted, but not translated. AccessToVB actually translates
Access syntax into Visual Basic sytax (Yes, Docmd.Openform "Employees", acDialog does
become Employees.show vbModal!)

If you have the evaluation version of AccessToVB, you may purchase the full version by
calling (212) 480-8217. The price is $395, plus shipping.
======================

Good Luck George! If there is anything more I can still do to assist you, please don't hesitate
to let me know. Thanks again for using MSDN Newsgroup!

Best regards,

Billy Yao
Microsoft Online Support

 

[George Aslanis]

We looked at some 3rd party offerings, but were not impressed with the
generated code. At this point we are just looking for source code (vb/vba)
to enumerate through the access collections to retrieve all of the control
types and relative position info used in each form/report. This will enable
us to programmatically dump to text files all of the form/report objects.
With a simple copy/paste function to obtain the module code, we will have a
good starting point. Far better than having to recreate everything from
scratch.

... and beware that the note mentioned VB4 or VB5 so the conversion software
is aimed at Access97 or earlier.

Since Access 2K uses VBA 6 (equivalent of stand-alone VB6), it is likely
that anything new in Access2K / VBA6 won't be converted correctly.

--
HTH
Van T. Dinh
MVP (Access)

Hi George,

Thank you for using MSDN Newsgroup! It's my pleasure to assist you with this issue.

I think Doug has pointed out ways to convert Access to VB6 but you

should
be aware that the

structural and object model differences are sufficiently great that no product can convert a
"good Access database" to a "good VB application".

We have had reports that third-party converters are a significant assist in such a conversion,
but there is still a great deal of manual work to be done. So I agree

with
Doug that it's maybe

better to redesign the Access Objects in VB rather than convert them

just
using a tool.

If you'd really like to, you can try Greenwich Financial Modeling, Inc.

at

http://www.GFMinc.com
who has a program AccessToVB. Below are a few quotes from their

Readme.txt
you might

find helpful for you:

======================

AccessToVB requires the following files be installed and registered for proper functionality:

EITHER Microsoft Visual Basic 4.0 Professional or Enterprise Edition
OR Microsoft Visual Basic 5.0 Professional or Enterprise Edition
Microsoft Access 97
EITHER the Sheridan Data Widgets 2.0
OR the GreenTree DataList 1.0 OCX controls
OR the Sheridan Data Widgets 3.0

None of the above programs are included with Access97ToVB. If you are converting paged
forms or tabbed forms into a VB 5 project, you must have VB 5 Service

Pack
2 or later.

If you have the Sheridan Data Widgets 2.0 controls, you must have at

least
version 2.0b (Build

186). If you have the GreenTree DataList controls, you must have

version
1.0d or higher. At

the time of this writing, the current version of the Sheridan control is 2.0c (Build 198), and the
current version of the GreenTree control is 1.0h (build 39).

Microsoft
Visual Basic 5.0

programs. AccessToVB analyzes the database, and then converts the

forms,

macros,
modules, and code behind forms to Visual Basic.

There are a number of user selectable options, including which forms and modules to convert,
the choice of custom controls supported, and the ability to convert the project to an MDI
project. All standard Access controls are converted, including the new

Tab

control.

Unlike competing programs, AccessToVB also converts: secured databases, menus,
macros, toolbars, and paged forms. AccessToVB also converts multicolumn list boxes and
combo boxes, in both bound and Value List mode. Another serious shortcoming of competing
products is that the code is converted, but not translated. AccessToVB actually translates
Access syntax into Visual Basic sytax (Yes, Docmd.Openform "Employees", acDialog does
become Employees.show vbModal!)

If you have the evaluation version of AccessToVB, you may purchase the full version by
calling (212) 480-8217. The price is $395, plus shipping.
======================

Good Luck George! If there is anything more I can still do to assist

you,
please don't hesitate

to let me know. Thanks again for using MSDN Newsgroup!

Best regards,

Billy Yao
Microsoft Online Support

 

[Douglas J. Steele]

The Documenter will show all properties, including Top and Left.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

We looked at some 3rd party offerings, but were not impressed with the
generated code. At this point we are just looking for source code (vb/vba)
to enumerate through the access collections to retrieve all of the control
types and relative position info used in each form/report. This will enable
us to programmatically dump to text files all of the form/report objects.
With a simple copy/paste function to obtain the module code, we will have a
good starting point. Far better than having to recreate everything from
scratch.

... and beware that the note mentioned VB4 or VB5 so the conversion software
is aimed at Access97 or earlier.

Since Access 2K uses VBA 6 (equivalent of stand-alone VB6), it is likely
that anything new in Access2K / VBA6 won't be converted correctly.

--
HTH
Van T. Dinh
MVP (Access)

Hi George,

Thank you for using MSDN Newsgroup! It's my pleasure to assist you

with
this issue.

I think Doug has pointed out ways to convert Access to VB6 but you

should
be aware that the

structural and object model differences are sufficiently great that no product can convert a
"good Access database" to a "good VB application".

We have had reports that third-party converters are a significant

assist
in such a conversion,

but there is still a great deal of manual work to be done. So I agree

with
Doug that it's maybe

better to redesign the Access Objects in VB rather than convert them

just
using a tool.

If you'd really like to, you can try Greenwich Financial Modeling,

Inc.

at Readme.txt
you might for
proper functionality: Pack
2 or later. least
version 2.0b (Build version
1.0d or higher. At is
2.0c (Build 198), and the Microsoft
Visual Basic 5.0 forms, and
modules to convert, the
project to an MDI Tab databases,
menus, multicolumn
list boxes and "Employees",
acDialog does you,
please don't hesitate