What error are you getting?  And you may want to check your use of single and double quotes.

Do you have permissions to create tables? 

You could either create them in advance and TRUNCATE them at the head of the stored procedure, or create them within the stored...

Here is an easy solution.  You may want to think through this and develop a UDF if you end up doing this quit a bit or more fields become involved. ...

Or use the REPLACE function on the field you are comparing and strip the apostrophe out completely when comparing [ LIKE ]. 

Correct.  I was just working under the assumption they had a populated Quarter table... 

If you already have a Quarter table, this may work as well. 

CREATE TABLE #Person( [ID] integer,

                                     [Name] varchar(20))

INSERT INTO #Person

SELECT 1, 'Joe Smith'

UNION ALL

SELECT...

Are your Employee.hzip4, dbo.Ranged.Start, and dbo.Ranged.Stop all four character fields since they are already aligned with the 5 digit zip used in the US? 

Also, there is an interesting article in...

Can you post your DELETE code? 

Can you give the output from Remi's code, because that seems very odd.  Maybe include UserID; remember to use that in the GROUP BY as well...

Here is yet another example.  It is for one record passed in from a front-end application.  This particular stored procedure, (which would probably be better as a UDF, uses the pipe...

INSERT INTO server1.base.dbo.table1( Field1) SELECT Field1 FROM dbo.table2

Here is a very slick method that Frank Kalis showed me.  (It took me a while of Private Posts offline to get it - I am a little thick sometimes...). ...

(dbo.User_CIS.Installment_Total_Fee * power(1 + (0.16 / dbo.User_CIS.Length_Installment),(dbo.User_CIS.Length_Installment*1)))

It looked like you parenthesis were a bit off and you did not need the select.  Why are you multiplying...

Doesn't it also shrink when you back it up? 

AdamMechanic, I am LOVING the new avatar!  "Sprinkle 'da floower..., sprinkle 'da floower..."