resolved this on my own so please disregard post now.

I got some help on this here, therefore this question is resolved:

http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_21755167.html

true dat...

It's very complex, that's the best I can do to explain, I've taken the time to provide you all the details so what are you needing at this point that...

no more issues here, I've figured it out...thanks

ST is just an inconsistency, I forgot to put UU in my post.  Thanks for the suggestion!

what do you mean the method chosen isn't a bright idea.  So you're saying using a stored proc initially to bring in one value is bad?  The stored proc is...

I ended up having to do a retarded workaround. I had to call my stored proc to move the result into a table then call another stored proc to retrieve...

crap, it hs nothing to do with the date, I am still getting dups

Thanks so much!  I put in '' for the onhold dates because I'm not using them in my where clause so they're not needed

hold on, you may have something..which date field?

The unique identifyer in payhistory is number.  So the 2 $200 has 1186 for m.number...it should only be showing 1 result, not 2..it's duplicating it.  Same for customer 000002 with...

yes, my inner query does produce muiltiple records which is not wrong...however I just added DISTINCT to it to solve that problem.   Now back to why this isn't working!

Your query to test using UNIONs produces syntax errors:

Msg 156, Level 15, State 1, Line 2

Incorrect syntax near the keyword 'As'.

Msg 170, Level 15, State 1, Line 47

Line 47:...

it's actually "DCR", not DR..I changed it to DR for privacy purposes so don't be alarmed, that's not the problem:

dcr table:         http://www.photopizzaz.biz/drscript.txt

customer table: http://www.photopizzaz.biz/customerscript.txt

master table:    http://www.photopizzaz.biz/masterscript.txt