RE: SQL DECLARE CURSOR preference

If the goal is to unify the look of the code going forward, then why not talk it out among the team and see if everyone can agree to a particular style? They'll be far more likely to adhere if they have buy-in, and if your team gets in the habit of looking at each others' code (informal code review) you'll be in >the habit of discussing more substantial coding habits (refactoring?) as well as matters of style.

--buck

Don't forget that you standard may need to change. I've seen code standards written 15 or more years ago in use. Occasionally you have to look to see what is outdated.
I programmed for a department of where the code had been done over the years by different consulting companies, or in house coders. It was several different styles. We finally became all in house and with a group of programmers who had a company standard. Now I had to program to that standard. From their viewpoint we were now programming to the company standard. My viewpoint at the time, I was just adding another coding style to the group of programs I work on.
-