Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > Using Forums Forums > Where is the Forum For…? > Guidance on converting and integrating legacy VB6.0/MSAccess monster app.
Ask a questionAsk a question
Search Forums:
 

QuestionGuidance on converting and integrating legacy VB6.0/MSAccess monster app.

  • Tuesday, November 03, 2009 8:01 PMdbstrat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    My current role in my ISV has me tasked with converting a huge monolithic MSAccess application that deployed at dozens of clients.  I am the only one here with the tools right now to be able to manage this project, but I am looking for guidance from those who have made similar prior efforts.

    Management believes that we can slowly break off subsystems and basically follow a continual EAI path where little by little pieces of the app move from MSAccess to Asp.Net.

    We have been going in this direction for a while now and the more we try the more like it seems like a really bad idea vs. trying to just write a new system with the lessons learned and not try to build on top of and integrate with a legacy architecture that frankly is a mess for various reasons, not the least of which is the mere fact that everything is designed around what Access can easily consume.

    Which would be the best forum to get this type of guidance?
     

All Replies