hmm...weird...here's what I'd actually posted...

John - I believe the query is checking for "InvoiceTotals.[Total Net]" not being zero first...

John - I believe the query is checking for "InvoiceTotals.[Total Net]" not being zero first...

Read BOL on datetime datatypes...

SQL Server recognizes date and time data enclosed in single quotation marks (') in these formats: 

Alphabetic date formats (for example, 'April 15, 1998')


Numeric date...

I don't have time to test the query I posted but it should work based on the order of execution of a select statement...here's the outlined sequence from the (in)famous...

I'm not quite sure but I think it has to do with the "order of execution"...

Try this as well...

select StaffDetails.[Employee],
ISNULL(SUM(InvoiceTotals.[Total Net]), 0) AS TotalNet,
ISNULL(SUM(InvoiceTotals.[Total CostBC]), 0) AS TotalCost
from StaffDetails...

You are probably using an inner join in your query and since there's no match for "MNO" in the "InvoiceTables" you don't see a result for that employee - change...

My David...aren't you a right old Narcissus ?!?! Where's all that understated British modesty that we hear so much about ?!

Martin - if you mean a "concierge" he really doesn't do all the stuff you want done - wrong person...I've already hired the person that you want...maybe I'll rent him...

"Quit and get another job" is really much easier said than done...you can be high-principled and quit, but the principles aren't going to pay the bills...

I have just been talking...

I've fantasised about this for so long that I don't have to pause to think - a FACTOTUM - affectionately called "Facty" - my genie that I shall summon simply...

At least your "trigger moments" are very few and far between - mine're increasing at an alarming frequency..

However, I do not think you can...

You'd have to use dynamic sql for this...also, your select should be a "set"..

DECLARE @UseIt1 as varchar(100)
EXEC ('SET ' + @UseIt1 + ' = 1')

They're identical - less wordy with using "between"...

In fact, internally, SQL Server treats a "between" as ">= and <="..

Two ways of checking this..

1) look at the execution plan for both

2)...

aah.."studies" are a whole new story altogether - almost all of them state the obvious - some of the more remarkable ones being:

1) Older parents raise babies' health risks.

2) More...

thanks for the update - else folks may have spent hours trying to get to the bottom of this one..