He needs to query the system tables... not to get their columns info .

Really depends on the indexes... I like the exists better but the left join does the job really well .

Select T1.* from dbo.Table1 T1 where not exists (Select * from dbo.Table2 T2 where T2.colid = T1.Colid /*all the other conditions you need and T2. = T1...*/)

Check out SQLDMO (VB). It may be your next best friend.

It'll be displayed in the newsletter tommorrow, you'll most likely get an answer.

"I do have one other question though.....if you go to this link:

http://test.rbrsystems.us/entergas.asp"

you're not validating any parameters.. this can be dangerous.

Read this :

The Curse and Blessings of Dynamic SQL

I'm not the expert on permission about mails.. However I know it's a security breach to give normal users access to that proc. It's best to have a job...

"It's because of rule 1 about databases: everybody thinks he's an expert."

You can blame MS Access for this one... It's nice to have wizards but it doesn't mean you...

I'll take that bet... and lose .

Seriously we usually don't answer when we can't and since I have 0 experience with replication and Yukon...

CREATE PROCEDURE dbo.emailgas --might wanna add the paramers in here

AS

EXEC master..xp_sendmail

@recipients = 'brad@domain.com',

@subject = 'SQL Server - Updated Gas Transaction',

@message =...

as he said .

It's a shame... I have neither .

Ya, ya... I'm trying to slow down .

Can you post the code of the proc?

I did.. already re-replied there .

The worst that will happen is that you'll get a call that the guy can't connect no more... But I don't think you will get it