locked
How do I convert Access 2003 / VBA app to a VB.NET app? RRS feed

  • Question

  • Hello,

    I have done some research on converting an existing app to VB.NET, but have not found what I am looking for.

    My existing app is currently created in Access 2003 VBA using access forms, modules, tables queries etc., and would like to convert all of it to VB.NET.

    What would be the best method or tools to use to accomplish this? The VB.NET app would be developed from VisualStudio 2005...

    ... or, would it be just as  easy to recreate the app from scratch?

    Thanks in advance.

    Monday, January 29, 2007 6:01 PM

Answers

  • Although VBA is a close cousing of VB6 you may have issues doing a direct upgrade using the upgrade wizard.  You can also try using the new

    Microsoft Interop Forms Toolkit 1.0
    This toolkit helps you bring the power of .NET to your existing Visual Basic 6 applications, by allowing them to display .NET WinForms from within the same application. Instead of upgrading the entire code base, these applications can now be extended one form at a time. The goal is a phased upgrade, with production releases at the end of each iteration containing both Visual Basic 6 and Visual Basic .NET forms running in the same Visual Basic 6 .exe process.

    ( http://msdn2.microsoft.com/en-us/vbasic/aa701259.aspx ) which may help you with a phased upgrade....However once agin you may have issues since this is not a standalone VB6 app...

    Personally I would start from scratch with a new VB.NET project and then try to upgrade one class at a time using the provided upgrade wizard

    Monday, January 29, 2007 6:34 PM

All replies

  • Although VBA is a close cousing of VB6 you may have issues doing a direct upgrade using the upgrade wizard.  You can also try using the new

    Microsoft Interop Forms Toolkit 1.0
    This toolkit helps you bring the power of .NET to your existing Visual Basic 6 applications, by allowing them to display .NET WinForms from within the same application. Instead of upgrading the entire code base, these applications can now be extended one form at a time. The goal is a phased upgrade, with production releases at the end of each iteration containing both Visual Basic 6 and Visual Basic .NET forms running in the same Visual Basic 6 .exe process.

    ( http://msdn2.microsoft.com/en-us/vbasic/aa701259.aspx ) which may help you with a phased upgrade....However once agin you may have issues since this is not a standalone VB6 app...

    Personally I would start from scratch with a new VB.NET project and then try to upgrade one class at a time using the provided upgrade wizard

    Monday, January 29, 2007 6:34 PM
  • Thanks for the advice DMan1.

    The upgrade wizard, are you referring to the "Create new project form existing code" option when creating a new VB.NET project?

    Wednesday, January 31, 2007 2:15 PM
  • Rashar,

    I'm looking at doing a similar thing soon - can you tell me if you have had any luck? What approach did you end up taking?
    Tuesday, July 17, 2007 3:14 AM
  • I too am looking to convert from Access 2003 to Dot Net.

    I suspect the database I am working with will have a number of coding issues and it might be easier to start from scratch.

    Any advice for someone with no experience?
    Wednesday, October 1, 2008 7:38 AM
  • Microtools' Access Whiz may be able to help you. Their url is http://www.microtools.us/anetvb8.aspx.
    Saturday, December 19, 2009 4:30 AM
  • Have you tried an Access to VB.NET converter, such as the one from Redbrook Technology? It's pretty damn good - Evolution Access to VB.NET converter , and only costs about $200.

    https://www.accessconverter.com/



    Software developer



    • Edited by Jim Dunstan Friday, September 4, 2020 10:51 AM
    Thursday, January 10, 2013 12:58 PM