Someone wrote a complicated view once. It was used in a stored procedure, but since it didn't have all the columns the proc needed, joined back to the tables that the view was based on to get the necessary additional data. Performance was bad, and when they took the logic of the view and put it directly into the proc where they could get the additional columns, performance was now better. So, boss decreed that views are "bad" and are not to be used. (This happened all before I started working there.)
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes