Or

Select Whse, count(Distinct Batch) from dbo.YourTable group by Whse

Select whse, batch, count(*) as Total

from dbo.YourTable

group by Whse, Batch

[Edit]

Sorry didn't understand the post correctly... gonna repost the right answer.

It's surely something stupid but I don't see it.

Hmm, this returns nothing for me (tried modifying the dateformat)?

Have you tried recompiling the procs right after you modified 'em (making sure that the old plan gets dropped).

Sorry for the delay, I just got released from the hospital.

Well first of all, you don't rollback the transaction after the first sp_executesql when there's an error. Is this...

The question is now : how do you know which records that you do no want?

Sounds like a good idea to me. The question really is wheater the server is allowing the production to keep on going without have too many indexes that...

Here's an exemple of a count of business days between 2 dates (excluding saturdays). It also takes into consideration the holidays. Msg me if you need help modifying...

You'd be better off with (18,6) because you got up to 6 decimals in that data sample.

This works for me :

If you need to have one proc for the min, and one for the max, I'll resplit them for you.

if exists (select * from dbo.sysobjects...

Let me send an ambulance to Frank's house before you post this...

I'll be waiting for mine here on the floor.

I'll have to believe you because I never used Crystal report... but I would assume that it's more complete than Access.

I don't mind... but it's gonna cost you 4 tickets to send me back.. probabely not best the investement you could make .

So...

So you need my adress to ship the tickets (I'd need one for my cat too)?