>>EM actually produces a script that was similar to the method described in a previous post; instead of adding a new column then drop / rename; the script generates a...

Check for any other account it may be using and failing. Change the last section to:

Select

*

From

@ErrorLog

Where

ProcessInfo...

Could definitely be the case. Did you check the SQL error log to see if there were any login errors?  That will tell you if it is at least getting...

A local account, even a local admin, does not have access rights to other machines. I would suggest setting up a SQL account specifically for replication. Make the same account...

I see that you are using Windows authentication. Are you using a domain account or a local account?

I didn't realize that the subscriber was the SQL 2000 instance on the same machine. Didn't you say that you had set both of them up to replicate themselves and...

Are you using the instance name for the suscriber?

Check the error log to see if there was anything logged about the login attempt.

Can you script out what you have done...

Beyond that, you may want to look at indexing. Start by making sure every column that is involved in a join is indexed.

I would advise not using a trigger for this because if the trigger fails, the transaction that fired it will be rolled back. You don't want to hear that your...

Not much to add to what has already been said. In my opinion, if a Text column is not trully needed or it is determined that it can be lived...

Using separate databases makes managing security easier as well. You don't have to pick and choose which objects each database should be able to access.

Of course, if this was SQL...

Please explain how you are trying to create the subscription. Are you using the wizard or stored procedures? If using stored procedures, please post the code.

Also, if you are using...

If you turn on "Include Client Statistics" it will show you the total time and the time spent processing the returned data by the client. The difference between the two...

Status column is for internal use only. The values have not been officially published. I do not know if they have been unofficially published.

This has been replaced in SQL 2005...

SELECT @@VERSION will always return the version of the server to which you are connected. It will not tell you the version of your client tools. I no longer have...