the guy who wrote it is really protective of his code too

if i change anything he has a paddy

i have found myself approaching things in a rubbish way just to stay common with the existing methods

i wrote a couple of table functions and he had a paddy because they weren't stored proceedure (full of unions :-))

if anyone has any ideas how to deal with someone like that then please let me know