How do you ix a broken database when you can't touch the Back End?

lemon_balm

Registered User.
Local time
Today, 08:44
Joined
Feb 7, 2006
Messages
65
I have been asked to take a database created last year and re-design it to make it more user-friendly.
Not a problem, I thought when asked but I am running into a little problem...(the database designer)
In my opinion, to make a system more user-friendly there is a necessity to access the code and tables in order to gain a reasonable knowledge of the way in which it has been constructed. Unfortunately, although I am allowed to LOOK at the front end, I am not allowed any further access to coding or back end information.
At present middle management are siding with the database designer as they feel that from a security standpoint, access needs controlling (I can agree with this to an extent)
Does anyone have any ideas of how I can talk the management round or any suggestions for a way through this issue?
(Oh, and I'm not allowed to build them a new database and substitute it...I already asked)

Regards

Jason
 
If they want a car repaired, do they allow the mechanic to drive it, I wonder?
 
Are you living in the Dilbert comic strip?

Sounds like the designer of the database should be the one to make his/her application more user friendly since they will not allow you to access the design of the database objects or the actual VBA code.

You will not be able to make any changes to the application since you do not have the necessary edit permission's to the database objects.

Why are they wasting your time with this rubbish? Sounds like you work for a government agency.
 
Me too.
The reason I am being asked is because he did such an awful job in the first place. We need to go over his head but first I need to get the middle management onside

Jason
 
is the security issue with the db design or the data? maybe they can give you an empty copy.
 
Nice idea Wazz, I'll see what I can do but it's like getting blood from a stone in this place. From the companies point of view I would say it is a data issue although I am authorised to both use, update and view it. However, the problems are coming from the database designer throwing a paddy over me having his database. I wonder if it is pride or whether he is trying to hide something...?
 
I think you need a senior manager to issue a JFDI instruction. (Just f...... do it).
 
Whats your role as opposed to the designer?

R u taking over completely - in which case its understandable - he's looking after his job.

Or are you doing a bit of work and then handing it back to him - again in which case its understandable - he would potentially have to fix your errors - if it all goes wrong.

Maybe the designer owns the db - in which case its understandable again.

The privacy of the data excuse seems a bit lame, as the designer I presume has access to the data.

I didn't offer any advice here - but I'd love to know what the reasons behind this are???
 
JFDI, LOL.... RTFM and JFDI ASAP LMAO

I wonder how much of a coherent sentence we can make with stuff like that....

I love JFDI, I will be using that :)
 
Neil - That's the route we're having to take now. He has been over-ruled

Paul - To answer some of your questions, I myself am also a database designer and so can appreciate why he is dragging his heels. I am not taking over his role in any way but will be taking control of this particular database. This is due to the urgency of getting it updated and running correctly. At present there is a large amount of risk involved with it not being used and the end users nationally refuse to work with a database that doesn't meet their needs. MR. X as he shall be known has failed to realise the urgency of this project or accept that there is an issue which needs to be resolved. He is not the owner of the dB and from what I can make of the system so far, it will be me fixing his errors, not the other way around.

Jason
 
Thanks Paul

Hopefully it should go without incident now but who knows.

Regards

Jason
 

Users who are viewing this thread

Back
Top Bottom