Or try this:

SELECT T1.first, T1.last

FROM

table1 T1

LEFT JOIN

table2 T2

ON

T1.First = T2.First AND

T1.Last = T2.Last

WHERE

T2.First IS NULL

You need to evaluate your expression so that datatypes are common and explicitly CAST them to common datatypes when needed (implicitly allowing SQL to deteremine this does not behave the...

If the datatype is of the character types then you can have a default of '' or an empty string. Other types don't allow this like this.

So I know we are are the same page (or heck, even the same book at this point). Simon will you post an example of what you are doing so...

Then you are talkign abou doing the code lik so

rs.CursorLocation = adUseServer

but when using adCmdStoredProcedure as the CommandType for the command object there is a know bug that the cursor...

Either you will need to enforce NOT NULL thru a trigger, checking field on INSERT in trigger, do the logic client side or use a Stored Procedure with the logic...

Cool I have now learned something new.

I'll have to test at home when I get a chance but I will pass anything I find back to the thread.

I don't believ so, could be triggers on the table you don't remember. But again your best bet to find the answers is to watch the DB with SQL Profiler...

Sounds right to me.

There is a lot to restoring a 6.x database. You have to recreate the database device in the same manner it was create perviously, step by step, from it's smallest...

Ok did check out that a NULL was in the output. Not sure how you app works but if all you are concerned with is the final output then this...

See if this helps with reasoning

800000

200000

quote:

---

To follow up on the experimentation:

The strange thing about this is that the time stamp (milliseconds) that...

To the best of my knowledge the answer is no.

Not as default, no. You have to specify NOT NULL. Would be a nice feature thou. Might send a feature request to MS.