Re: Removing datasets from our architecture...
- From: "Andrew Faust" <andrew@xxxxxxxxxxxxxxx>
- Date: Sun, 11 Nov 2007 20:49:04 -0700
but its close to unmaintainable,
If that's true it might be worth the cost to make a change. You're going to need to do your own analysis of cost/time & benefit to decide that one.
Our main conundrum is that we have an access database that is falling over from too many users
By all means switch to something better. You don't necessarily need to completely overhaul all your code to make this change, though. Depending on how you built your app you may need to merely create a new database and change the connection string you are using to connect to the DB. ADO.Net is great about being database independent. So long as you aren't using database specific functionality you can often change DB types simply by changing the connection parameters and the actual type of DbConnection, DbCommand & DbDataAdapter objects created.
You should certainly take that in to consideration on your decision.
--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com
"John Sheppard" <nospam@xxxxxxxxxxxx> wrote in message news:fh6sdq02biq@xxxxxxxxxxxxxxxxxxxx
Yeah you are right,
I guess the existing code works, but its close to unmaintainable, so I wonder weather now is the time to jump ship to proper business objects instead of trying to hack around with datasets...
Our main conundrum is that we have an access database that is falling over from too many users, its not very well designed, and we are in a hurry to get it migrated.....
Thank you!
John
"Andrew Faust" <andrew@xxxxxxxxxxxxxxx> wrote in message news:730D729B-19DB-42B8-84A4-FA09BD1B1419@xxxxxxxxxxxxxxxxCode generators are great, and highly recommended. However, it's not worth ripping out working code unless you have a lot more DB code still needing to be written. You should not make the change merely for the sake of making the change. Only do so if the benefits in time/quality/maintenenance for the remainder of the project outweigh the time & risk of making a major change to functioning code.
--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com
"John Sheppard" <nospam@xxxxxxxxxxxx> wrote in message news:fh44sp021pi@xxxxxxxxxxxxxxxxxxxxHello,
I was curious as to peoples thoughts on using tools such as MyGeneration/CodeSmith to generate business objects as opposed to using datasets? We currently use datasets, for various reasons I *suspect* we want to move away from using them....
I guess my secondary question is will it be a complete rewrite to remove datasets from the application? :( or is there an easy way to do it? (They are HEAVILY used)
I wonder if we will be stuck with them forever more, or should I go through the pain of changing *now*, somewhat early in the development process, (6 months) ...or should I just live with them...
Background Info
MsAccess Backend, Webservice consumed by a WinForms application all in .net
Thank you for any thoughts anyone has...
John
.
- References:
- Removing datasets from our architecture...
- From: John Sheppard
- Re: Removing datasets from our architecture...
- From: Andrew Faust
- Re: Removing datasets from our architecture...
- From: John Sheppard
- Removing datasets from our architecture...
- Prev by Date: Re: Quest: VS.NET 2008 complete dev env and VS.NET 2008 version books track...
- Next by Date: Re: A newbie question
- Previous by thread: Re: Removing datasets from our architecture...
- Next by thread: Re: Removing datasets from our architecture...
- Index(es):
Relevant Pages
|