Suggest using XPSMTP instead. See

http://www.sqldev.net/xp/xpsmtp.htm

Going back to your original example - if you wanted an error if a table doesn't exists I would do somethin like this:

DECLARE @intErrorCode INT

IF OBJECT_ID('AdventureWorks.Person.AddressX') IS NULL

BEGIN

PRINT 'Table...

do you have a sample update statement?

Have you tried BEGIN TRY....

Oops - just realized this is a 2000 forum - nevermind

1) Create a trigger. See Books On Line - it is very easy to follow

2) Create a stored procedure and have it run as a SQL Server Agent job...

I belive you can only install Developer or Enterprise evaluation on XP. Which version are you trying to install?

Are you using nvarchar?

Set is recommended over select according to BOL.

See http://msdn2.microsoft.com/en-us/library/ms187330.aspx

Jason didn't mention "ArithAbort."

Try SET NUMERIC_ROUNDABORT OFF

Can't you just change the password? I have no knowledge of 6,5.

Draft the CREATE TABLE and INSERT statements so I can test on my machine. Set your question up for success.

Use the free SQL Server Upgrade Advisor

http://www.microsoft.com/downloads/details.aspx?FamilyID=1470e86b-7e05-4322-a677-95ab44f12d75&displaylang=en

c

Is there more than one instance on the box?

When you say "prepared statements" do you mean ad hoc queries? If so, the stored procedure is better. Security: By using only stored procedures you can avoid...