If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Clients with bad table design
Mostly I've been able to have complete control of table design on projects
I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#2
|
|||
|
|||
I would help them fix it and explain that it will save them time, money, and
frustration in the future. -- Rick B "Amy Blankenship" wrote in message ... Mostly I've been able to have complete control of table design on projects I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#3
|
|||
|
|||
I would encourage them to fix it and explain why. Not only will this save
them time and money in the long run, but if your application is based on a bad database design, YOUR application is going to be blamed when it doesn't work. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "Amy Blankenship" wrote in message ... Mostly I've been able to have complete control of table design on projects I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#4
|
|||
|
|||
Even if the direct client created this design and telling her this will let
her know you're not convinced she's as much of an Access expert as SHE thinks she is? -Amy "Roger Carlson" wrote in message ... I would encourage them to fix it and explain why. Not only will this save them time and money in the long run, but if your application is based on a bad database design, YOUR application is going to be blamed when it doesn't work. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "Amy Blankenship" wrote in message ... Mostly I've been able to have complete control of table design on projects I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#5
|
|||
|
|||
Amy Blankenship wrote: would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? Could there be a third way e.g. you build the tables using your correct design and create VIEWs/PROCEDUREs (Query objects) to present the data in the structure the front end application has anticipated? |
#6
|
|||
|
|||
In one of my past incarnations I was a remodeling contractor in NYC.
Sometimes I would look at jobs that couldn't be done properly because of existing conditions. I would advise the potential client of this, and would explain why I couldn't guarantee the results. If the person told me that another contractor had bid on the job and saw no problems with the existing conditions, I would reply that they should go with that person if they were confident in the results. Similarly, if the client in the midst of a job insisted on a particular approach I knew to be incorrect, I would tell them I could do it, but for time and materials rather than a contract price, and with no guarantees. Of course, it took me some years and much bitter experience to learn to walk away from those situations. I think Roger's observation that you will be blamed for future problems is a very serious consideration. Could you build a small sample database to demonstrate how your approach will improve certain areas? For instance, if the client needs to change multiple records when updating certain information, could you demonstrate the superiority of properly related data? "Amy Blankenship" wrote in message ... Even if the direct client created this design and telling her this will let her know you're not convinced she's as much of an Access expert as SHE thinks she is? -Amy "Roger Carlson" wrote in message ... I would encourage them to fix it and explain why. Not only will this save them time and money in the long run, but if your application is based on a bad database design, YOUR application is going to be blamed when it doesn't work. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "Amy Blankenship" wrote in message ... Mostly I've been able to have complete control of table design on projects I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#7
|
|||
|
|||
Well it does take a certain amount of tact.
"Well, I can see why you designed it the way you did, but now with this web front end..." or "Keeping the existing design has certain advantages, but if we change it, we can minimize the data integrity errors..." You don't have to say that their design is bad, just demonstrate the advantages of the new design. I've never worked as a contractor. I've always been "in-house". So I can't speak to whether you should walk away or not. You do have to make a living. However if the design is going to cause you problems that will send you over-budget, then your customer won't be happy and you will lose money too. (I gather you are bidding the job and not being paid by the hour.) This is called a "lose-lose". -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "Amy Blankenship" wrote in message ... Even if the direct client created this design and telling her this will let her know you're not convinced she's as much of an Access expert as SHE thinks she is? -Amy "Roger Carlson" wrote in message ... I would encourage them to fix it and explain why. Not only will this save them time and money in the long run, but if your application is based on a bad database design, YOUR application is going to be blamed when it doesn't work. -- --Roger Carlson Access Database Samples: www.rogersaccesslibrary.com Want answers to your Access questions in your Email? Free subscription: http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L "Amy Blankenship" wrote in message ... Mostly I've been able to have complete control of table design on projects I'm a part of. But recently I got a project *just* to add an ASP front end for a database. The design of the tables is horrible, and will cause lots of extra work for me. I'd think it has already cost them lots of extra work--I'm surprised they haven't noticed and fixed it. In my shoes, would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? -Amy |
#8
|
|||
|
|||
Interesting thought.
Thanks. -Amy wrote in message oups.com... Amy Blankenship wrote: would you advise the client that their data structure is bad and offer to redo it (and look like you're grabbing for more work) or keep your mouth shut and do what you were hired for? Could there be a third way e.g. you build the tables using your correct design and create VIEWs/PROCEDUREs (Query objects) to present the data in the structure the front end application has anticipated? |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Access combo box-show name, not ID, in table? | write on | New Users | 30 | April 30th, 2005 09:11 PM |
unable to repair inobox | Sudheer Mumbai | General Discussion | 1 | February 20th, 2005 11:55 AM |
Automatic filling of fields in table two from table one | Jim Kelly | Database Design | 1 | September 27th, 2004 10:16 PM |
Autonumber | Ally H. | General Discussion | 7 | August 27th, 2004 04:51 PM |
Table design for a booking system | Brian C | Database Design | 2 | April 27th, 2004 03:11 AM |