this for sure is a rather hasty approach and it does'nt seem to work..

so how exactly would you include that in the body of the message??

Yes thanks a lot!

I see what I was doing wrong..

this does not work as  the completiondate is a datetime field..

Also this query is a part of a scheduled task so it looks at the current system time..

create a trigger against the table..

never mind thanks Sushila I see what you are saying..

Ok I update the select statement as follows:

Insert DeletionHistory

Select deleted.Firmfile,SYSTEM_USER,Getdate() From SEARCH,deleted

    WHERE SEARCH.FirmFile = deleted.FirmFile

However nothing is recorded??

A given individuals performance far exceeds expectations when in face of competition. My personal belief is if you have a quality product or service to...

Thanks Chris

for a solution.. For all other posts agreed sql case in where clause is neat trick that is where I was hoping for correction on syntax.. So instead...

thanks, it's called not paying attention..

That was much better Here is what I found under the package logs..

Step Error Source: Microsoft Data Transformation Services (DTS) Package

Step Error Description:Logon failed: MapiLogonEx Failed due to MAPI error...

Kindly improvise on suggestion that will resolve the issue. I prefer simplicity.. Thanks..

It's not a permission issue because I am running this under admin account

The union and the left outer join was the most optimal way.. I had tried the union however the where clause does make it much more efficient ..

Execution time is...

This is definately not the correct approach a simple select shows that one of the record does exist in the list of tables. Remember users is the superset and the...