Migrating application from Microsoft Access to VB or C#.NET
I'm as of now attempting to persuade administration regarding the need to port one of our applications to .NET.
I basically know all the significant advantages of doing this, however now need to take a gander at how this can be accomplished in fact, so I can assemble a venture arrange.
Along these lines, my arrangement was to change over the inquiries into put away methods or potentially sees on the backend and re-compose the structures in WPF or WinForms.
Presently, the code is the place I unhinge. Is it conceivable to bundled up the code behind and modules into dlls and devour them while it is gradually ported to VB/C#?
What we can't be left with is a large portion of an application in VB/C# and half in Access, it must "show up" to all be one application, even part of the way through the movement.
Much appreciated ahead of time.
Alter: Just some more data about what we do and why we're taking a gander at moving far from Access.
We are basically an ISV and the Access application is our principle item. This application has been created over a time of 15 years, by numerous, numerous designers on an impromptu premise. There is no documentation for this application.
We likewise have issues with getting spreading in SCC to work appropriately, so we've right now got 4 or 5 code bases for the about six customers we have. On top of that, all the testing we do is totally manual, which you can envision is exceptionally work concentrated, and just begins to expose what's underneath of what truly should be tried.
We're at present hoping to grow, and have various prospective customers that are in the last stages. I'm stressed that with these new deals, will be overwhelmed with support and testing, and that this application will turn out to be significantly more ensnared a carriage.
I'll additionally add to this the way that we're going to enter the spec period of a fresh out of the box new item, which is in all likelihood going to be implicit .NET. If we somehow managed to revamp the Access application in .NET, at that point the general population we use for that can go straight on to this new improvement. If we somehow happened to remain in Access, at that point we'd need to get some new Access individuals in, whom would need to be retrained once we begin the new advancement.
So basically it has boiled down to two options, major refactoring work in Access to attempt and "sort out" the code somewhat better, and those of you who have proposed separating parts are most presumably right; I'm certain there are parts that are never again utilized. Notwithstanding, I expect that in the event that we remain in Access despite everything we won't have the capacity to work in powerful testing regardless we won't have legitimate SCC fanning, which will prompt bolster proceeding to be a bad dream, and any future advancements on this item makings things more regrettable. Whichever way there is a considerable measure of work that we're going to leave on, which is either going to be done in Acces, or .NET.
generate ASPX forms for CRUD in VB or C#, called CodeSpark. Use this will the Access converter, and it will take you a long way towards getting away from Access
I basically know all the significant advantages of doing this, however now need to take a gander at how this can be accomplished in fact, so I can assemble a venture arrange.
Along these lines, my arrangement was to change over the inquiries into put away methods or potentially sees on the backend and re-compose the structures in WPF or WinForms.
Presently, the code is the place I unhinge. Is it conceivable to bundled up the code behind and modules into dlls and devour them while it is gradually ported to VB/C#?
What we can't be left with is a large portion of an application in VB/C# and half in Access, it must "show up" to all be one application, even part of the way through the movement.
Much appreciated ahead of time.
Alter: Just some more data about what we do and why we're taking a gander at moving far from Access.
We are basically an ISV and the Access application is our principle item. This application has been created over a time of 15 years, by numerous, numerous designers on an impromptu premise. There is no documentation for this application.
We likewise have issues with getting spreading in SCC to work appropriately, so we've right now got 4 or 5 code bases for the about six customers we have. On top of that, all the testing we do is totally manual, which you can envision is exceptionally work concentrated, and just begins to expose what's underneath of what truly should be tried.
We're at present hoping to grow, and have various prospective customers that are in the last stages. I'm stressed that with these new deals, will be overwhelmed with support and testing, and that this application will turn out to be significantly more ensnared a carriage.
I'll additionally add to this the way that we're going to enter the spec period of a fresh out of the box new item, which is in all likelihood going to be implicit .NET. If we somehow managed to revamp the Access application in .NET, at that point the general population we use for that can go straight on to this new improvement. If we somehow happened to remain in Access, at that point we'd need to get some new Access individuals in, whom would need to be retrained once we begin the new advancement.
So basically it has boiled down to two options, major refactoring work in Access to attempt and "sort out" the code somewhat better, and those of you who have proposed separating parts are most presumably right; I'm certain there are parts that are never again utilized. Notwithstanding, I expect that in the event that we remain in Access despite everything we won't have the capacity to work in powerful testing regardless we won't have legitimate SCC fanning, which will prompt bolster proceeding to be a bad dream, and any future advancements on this item makings things more regrettable. Whichever way there is a considerable measure of work that we're going to leave on, which is either going to be done in Acces, or .NET.
Answer -
I would recommend using a conversion tool , such as Evolution MS Access Converter. This will replicate all of your Forms in VB.NET, and convert a lot of the code in modules (some code is not possible to convert directly, and will need some rethinking). It does a pretty good job of converting DAO and ADO code to ADO.NET too. The same company provide a free tool that will generate stored procedures for all tables in a database for CRUD operations, and will `generate ASPX forms for CRUD in VB or C#, called CodeSpark. Use this will the Access converter, and it will take you a long way towards getting away from Access
Comments
Post a Comment