Moving your MS Access Application to .NET. Can it be done ?
I been included in a considerable measure of movement tasks where one is changing over starting with one stage then onto the next. I've likewise observed terrific cost overwhelms, and tremendous under estimations of how troublesome these sorts of ventures can be.
In a portion of the ventures and stages I've made and that I had worked for about $25,000, the cost of supplanting this application and changing it brought about the other group of individuals assuming control over this venture and the subsequent cost was in overabundance of $750,000.
You're additionally making a presumption that the present framework should be supplanted. You MUST have clear in your mind what the genuine objectives of moving and supplanting the present stage and programming are. Just revising something and moving the usefulness over to another stage yields you practically nothing, with the exception of spending a considerable measure of cash that truly doesn't profit your business of all (however hello those designers will take the cash, in the event that they persuade you regarding the need of doing this)
It looks bad to take a flawlessly decent running application that has been running extraordinary for a long time and doing its occupation, and after that just revamp it in another stage, particularly on the off chance that you don't have the Manpower and ability and work force accessible to keep up this new framework. What's more, this is particularly more along these lines, if the new frameworks not going to fulfill much else besides what the past framework was doing. Truth be told on the off chance that you had that Manpower, they'd likely as of now have STARTED changing over this framework officially after some time. I mean why all of sudden all of a sudden did somebody toss a light switch and out of the blue understand that new engineers should be gotten to revise a framework that is as of now been running fine?
I'll likewise bring up having been in this business for quite a while (both distributed and specialized supervisor of get to books) I additionally done relocation ventures from centralized computer frameworks to desktops . Furthermore, I likewise done relocation of desktop database frameworks to expansive centralized server frameworks .
I can just say that it is uncommon to see an application with that many tables. Actually this issue raises alerts immediately.
As a result of such an expansive number of tables here, I need to imagine that there's possible either a lot of procedures, and different applications cobble together here that speaks to this entire framework . In the event that this is not the situation, at that point obviously reworking in .net does not bode well unless you address the un standardized nature of the framework. The way that the information is as of now in SQL server helps, yet that very well might imply that you had the torque and limit and framework to scale something that was ineffectively outlined and the primary spot
A major significant segment of programming adaptability originates from having appropriately standardized information models. The issue you have is that you have the information in SQL server, and it's exceptionally enticing to modify parts of the structures and usefulness as .net structures, and keep on using the current existing information models. Tragically this place you in somewhat of a stone and hard place, since you need to keep on using existing information, and begin revising usefulness in .net. However modifying of usefulness in .net without tending to the information models is an awful thought.
In an amusing touch of destiny, this is a difficult situation, in light of the fact that possible if that framework had truly incredible awesome outlined information models, you won't not want to overhaul and move this into .net. Get to and SQL server can scale out to 100's of clients easily anway. Also, get to bolsters the utilization of class protests, and even source code control.
As it were remember that individuals may be making a request to revamp this in .net since they trust the application will then mystically have expanded adaptability, and have the capacity to be changed quicker then that of their changing business rules. Truth be told frequently the inverse happens, in light of the fact that get to is an extremely RAD apparatus. This implies the bleeding edge individuals can regularly make alterations because of business tenets changing, speedier than the IT Dept and their group of engineers working ceaselessly on the following awesome rendition of the application. Also, more regrettable you would prefer not to seat that IT Dept and those designers with a poor information display.
That is to say, would you say you are to now employ the IT division to manufacture each and every spreadsheet and exceed expectations for the general population in light of the fact that are present business procedures are not sufficiently adaptable? It would be brilliant if the IT Dept to head over to everyone's work area, hold their hand, and fabricate the exceed expectations sheets CORRECTLY for everyone, except it's not handy in this present reality. So notwithstanding removing access from these individuals, you should remove exceed expectations from them moreover.
I am simply calling attention to that my creepy crawly sense proposes to me that the information models here will be a genuine test. Recollect that, I would dependably take poor code and incredible planned information models over the turn around (Great code, yet unpleasant information models). The explanation behind this is with extraordinary information plans, at that point the code and applications for all intents and purposes keep in touch with themselves. Also, with incredible information models, at that point the simplicity of which you can change for the constantly changing business leads again supports awesome information outlines over that of extraordinary code. You can likewise RE calculate the code additional time WHEN you have great information models. Along these lines, with great information models you can move structures and usefulness and the UI over into .net, and you can do this flawlessly and effortlessly WHEN the current information models bode well to keep.
Likewise it looks bad to move to these new advances and less will present the likelihood of presenting things like self serve online interfaces for the current business forms. Thus, today we can now enable clients to control and utilize some of that data that is at present secured up in the framework. This may be basic as them checking the status of their requests as opposed to squandering profitable client telephone time. Or, then again it may be something basic like how a noteworthy bundle organization in Canada spared an expected $10,000,000 in the principal year of actualizing their bundle following framework. Or, on the other hand may be something as straightforward as enabling the client to look into their record adjust.
So at this moment in the commercial center, these self serve client web-based interface frameworks enable clients to enter and utilize and get at their data rather than the ringing some utilized inside the association who at that point pivots and dispatches the application and after that controls the data for that client while on the telephone. May very well also let the client do this work! So from request status, to balances owing, to keeping money, or what ever it is, the genuine cherry model ticket today is to enable the client to use at a cell serve online interface that speaks to all that profitable data that that interior application is making .
As specified, you need to ask, is the place is the Manpower and staff going to come to construct and keep up this application? Clearly the current framework with huge quantities of structures and tables you are tossing out must by one means or another been made, and speaks to some noteworthy speculations of time and endeavors . The key idea you need to ask, is the place were those critical speculations and assets originating from to manufacture that current application? Who will keep up the new framework at that point? As it were you have to outline the new framework to lessen upkeep costs. (new forms of my product can decrease support by as much as 10 or 15 hours for every year for client ).
Toward the day's end, great programming advancement and great outlines are great plans. Utilizing Access, or VB6, or vb.net don't make a difference if the framework is meeting your business needs now.
I ought to likewise bring up that the new form of get to 2010, can make .web frames. They are XAML (zammel .net structures). I am guiding this out, in light of the fact that changing the front end skin from access toward .net yields you VERY minimal unless the hidden information structures and plans are likewise adjusted to take points of interest of new conceivable business forms that can be refined with new innovations, (for example, those cell serve online interfaces). Just repaint the textual style closes with .net structures is truly particularly sums to a misuse of cash as I would like to think UNLESS different issues are being tended to, for example, the information model, or some kind of online interface that'll enhance adaptability here.
You have some extraordinary exhortation here as of now. Remember this truly comes down to what are the objectives and purposes behind these individuals craving this product to be revamped in .net. Those new objectives and longings better not be founded on the appearance of basically revamping the structures you have now into .net as that will truly finish nothing by any stretch of the imagination, and won't enhance their capacity to address their changing business needs that the framework they are presently utilizing clearly had been doing previously.
Good fortunes on this I don't think this is the sort of question that can be replied in a basic gathering post, however at any rate you have parts to bite on here so you can take care of business.
In a portion of the ventures and stages I've made and that I had worked for about $25,000, the cost of supplanting this application and changing it brought about the other group of individuals assuming control over this venture and the subsequent cost was in overabundance of $750,000.
You're additionally making a presumption that the present framework should be supplanted. You MUST have clear in your mind what the genuine objectives of moving and supplanting the present stage and programming are. Just revising something and moving the usefulness over to another stage yields you practically nothing, with the exception of spending a considerable measure of cash that truly doesn't profit your business of all (however hello those designers will take the cash, in the event that they persuade you regarding the need of doing this)
It looks bad to take a flawlessly decent running application that has been running extraordinary for a long time and doing its occupation, and after that just revamp it in another stage, particularly on the off chance that you don't have the Manpower and ability and work force accessible to keep up this new framework. What's more, this is particularly more along these lines, if the new frameworks not going to fulfill much else besides what the past framework was doing. Truth be told on the off chance that you had that Manpower, they'd likely as of now have STARTED changing over this framework officially after some time. I mean why all of sudden all of a sudden did somebody toss a light switch and out of the blue understand that new engineers should be gotten to revise a framework that is as of now been running fine?
I'll likewise bring up having been in this business for quite a while (both distributed and specialized supervisor of get to books) I additionally done relocation ventures from centralized computer frameworks to desktops . Furthermore, I likewise done relocation of desktop database frameworks to expansive centralized server frameworks .
I can just say that it is uncommon to see an application with that many tables. Actually this issue raises alerts immediately.
As a result of such an expansive number of tables here, I need to imagine that there's possible either a lot of procedures, and different applications cobble together here that speaks to this entire framework . In the event that this is not the situation, at that point obviously reworking in .net does not bode well unless you address the un standardized nature of the framework. The way that the information is as of now in SQL server helps, yet that very well might imply that you had the torque and limit and framework to scale something that was ineffectively outlined and the primary spot
A major significant segment of programming adaptability originates from having appropriately standardized information models. The issue you have is that you have the information in SQL server, and it's exceptionally enticing to modify parts of the structures and usefulness as .net structures, and keep on using the current existing information models. Tragically this place you in somewhat of a stone and hard place, since you need to keep on using existing information, and begin revising usefulness in .net. However modifying of usefulness in .net without tending to the information models is an awful thought.
In an amusing touch of destiny, this is a difficult situation, in light of the fact that possible if that framework had truly incredible awesome outlined information models, you won't not want to overhaul and move this into .net. Get to and SQL server can scale out to 100's of clients easily anway. Also, get to bolsters the utilization of class protests, and even source code control.
As it were remember that individuals may be making a request to revamp this in .net since they trust the application will then mystically have expanded adaptability, and have the capacity to be changed quicker then that of their changing business rules. Truth be told frequently the inverse happens, in light of the fact that get to is an extremely RAD apparatus. This implies the bleeding edge individuals can regularly make alterations because of business tenets changing, speedier than the IT Dept and their group of engineers working ceaselessly on the following awesome rendition of the application. Also, more regrettable you would prefer not to seat that IT Dept and those designers with a poor information display.
That is to say, would you say you are to now employ the IT division to manufacture each and every spreadsheet and exceed expectations for the general population in light of the fact that are present business procedures are not sufficiently adaptable? It would be brilliant if the IT Dept to head over to everyone's work area, hold their hand, and fabricate the exceed expectations sheets CORRECTLY for everyone, except it's not handy in this present reality. So notwithstanding removing access from these individuals, you should remove exceed expectations from them moreover.
I am simply calling attention to that my creepy crawly sense proposes to me that the information models here will be a genuine test. Recollect that, I would dependably take poor code and incredible planned information models over the turn around (Great code, yet unpleasant information models). The explanation behind this is with extraordinary information plans, at that point the code and applications for all intents and purposes keep in touch with themselves. Also, with incredible information models, at that point the simplicity of which you can change for the constantly changing business leads again supports awesome information outlines over that of extraordinary code. You can likewise RE calculate the code additional time WHEN you have great information models. Along these lines, with great information models you can move structures and usefulness and the UI over into .net, and you can do this flawlessly and effortlessly WHEN the current information models bode well to keep.
Likewise it looks bad to move to these new advances and less will present the likelihood of presenting things like self serve online interfaces for the current business forms. Thus, today we can now enable clients to control and utilize some of that data that is at present secured up in the framework. This may be basic as them checking the status of their requests as opposed to squandering profitable client telephone time. Or, then again it may be something basic like how a noteworthy bundle organization in Canada spared an expected $10,000,000 in the principal year of actualizing their bundle following framework. Or, on the other hand may be something as straightforward as enabling the client to look into their record adjust.
So at this moment in the commercial center, these self serve client web-based interface frameworks enable clients to enter and utilize and get at their data rather than the ringing some utilized inside the association who at that point pivots and dispatches the application and after that controls the data for that client while on the telephone. May very well also let the client do this work! So from request status, to balances owing, to keeping money, or what ever it is, the genuine cherry model ticket today is to enable the client to use at a cell serve online interface that speaks to all that profitable data that that interior application is making .
As specified, you need to ask, is the place is the Manpower and staff going to come to construct and keep up this application? Clearly the current framework with huge quantities of structures and tables you are tossing out must by one means or another been made, and speaks to some noteworthy speculations of time and endeavors . The key idea you need to ask, is the place were those critical speculations and assets originating from to manufacture that current application? Who will keep up the new framework at that point? As it were you have to outline the new framework to lessen upkeep costs. (new forms of my product can decrease support by as much as 10 or 15 hours for every year for client ).
Toward the day's end, great programming advancement and great outlines are great plans. Utilizing Access, or VB6, or vb.net don't make a difference if the framework is meeting your business needs now.
I ought to likewise bring up that the new form of get to 2010, can make .web frames. They are XAML (zammel .net structures). I am guiding this out, in light of the fact that changing the front end skin from access toward .net yields you VERY minimal unless the hidden information structures and plans are likewise adjusted to take points of interest of new conceivable business forms that can be refined with new innovations, (for example, those cell serve online interfaces). Just repaint the textual style closes with .net structures is truly particularly sums to a misuse of cash as I would like to think UNLESS different issues are being tended to, for example, the information model, or some kind of online interface that'll enhance adaptability here.
You have some extraordinary exhortation here as of now. Remember this truly comes down to what are the objectives and purposes behind these individuals craving this product to be revamped in .net. Those new objectives and longings better not be founded on the appearance of basically revamping the structures you have now into .net as that will truly finish nothing by any stretch of the imagination, and won't enhance their capacity to address their changing business needs that the framework they are presently utilizing clearly had been doing previously.
Good fortunes on this I don't think this is the sort of question that can be replied in a basic gathering post, however at any rate you have parts to bite on here so you can take care of business.
Comments
Post a Comment