quick question...

[smiley0q0]

in general which would be easier... to try and fix an old barely functioning database, inluding all reports, forms, queries.. etc,(a database i have never worked with) or just start from scratch and rebuild it.
i know it would depend on the complexity of the thing, and all that, but i am looking for a general consensus and honest answers...
thanks

 

[ghubbell]

Start from scratch Smiley! (my opinion...) Gord
ghubbell@total.net

 

[TheVMan]

I would say it would depend a lot on whether the original designer stuck to good design standards (or your design standards). So much is left for play in this question. If the level of complexity was low, and you can port the data easily into a new DB, then perhaps starting new and making it an application you are familiar with is your best option...if you have the time.

V

 

[smiley0q0]

thanks guys... i appreciate your input... i think i am going to rebuil it... so i will probably be asking quite a few questions for the next couple of days... : };o)

 

[dneufarth]

Just curious --

Is this for a business or paying client?

If it's barely functioning, is it needed at all?

Is cost versus benefit of any consideration to rectifying usability problem(s)?


Dave

 

[smiley0q0]

it's for business, it's barely functioning because the guy that i replaced used "band-aid" fixes for problems that arose with it. He fixed it so it worked for that month, then the next month another problem would come up, so he jerry-rigged it to make it look like it was right. now those "band-aid" fixes are the ones causing all the problems... and i can't understand where his logic was coming from, much less try to comprehend his sql!! %-( but that's ok cuz i'm gonna make it all better, (i'm going to use neosporin, so all the infections go away)