If you are using an access front end, you can use the rich text box control to display the text and highlight the results. I implemented a similar thing years...

Purists would argue that a balance column has no place in a correctly normalized database schema (except, perhaps, in a view) however I understand that there are circumstances where this...

No Problems. There are not a lot of options for this in 2000. My honest recommendation would be to write a simple app that periodically polls the queue and sends...

Well. One option would be to build the call to your mail proc dynamically:

DECLARE @Body1 NVARCHAR(8000),
        @Body2 NVARCHAR(8000),
     ...

Check out WAITFOR in BOL

Hmm.

SQL Server isn't really the ideal place to be sending emails from. Are you using SQLMail? CDO?

What is in the text? I've worked around it in the past by processing the text data in 8000 byte chunks. If you post a little more info, maybe we...

And if you INSIST on running this code on your server, add sp_OADestory @WordDocument in the end of your code to explicitly destory the COM object.

Basically you are instantiating a COM object in your PROC. You will also need Office (professional probably) installed on your server. I can't see anything else you would need.

Think about...

Try This:

Select TOP 100 PERCENT bp_group_name

FROM mf_01createbp_grp

WHERE bp_group_name NOT IN

(SELECT TOP 100 PERCENT

BPG.bp_group_name

FROM Eploltp01.sch_bpref.businesspartnergroup

ORDER BY bp_group_name)

Are you doing the order by in the subquery to create the conditions for a...

It is better if you only update local tables. You can rewrite your query to run on the remote server.

It's probably not the best solution, but you can do...

Cool, thanks for the follow-up Ninja. I always like learning new (and better) ways to approach a problem.

I agree, the correlated subquery is less than ideal and can get out of hand quickly. The other option I posted, the self join and group by, would probably perform...

One more PS... Just in case, If you are running SQL2005, use the ROW_NUMBER function.

ROW_NUMBER OVER(PARTITION BY ID1 ORDER BY ID2) AS SEQ

PS. the line:

AND t1.id <= t2.id    -- Supplimental Order by (to account for duplicates) 

is optional if your order by column is unique