We don't have an issue in determining when to issue the raiseerror condition, but being able from DOS being able to capture the error to determine to continue process other...

The developer can run the same copy function on our development box and gets the popup.  I don't know of any differences between our development environment and our production. 

I have a scheduled job that runs the following script on a daily basis...

exec master.dbo.xp_sendmail 'youremailaddress',

@subject=' Job Failures',

@query='

select b.server, a.name, b.step_name, b.sql_message_id, b.sql_severity,

       b.message

from msdb.dbo.sysjobs a, msdb.dbo.sysjobhistory b

where a.job_id...

This is what we did:

C drive is for the OS

D drive is for application (i.e. SQL Server, etc)

E drive is for database files

F drive is for backup files

drive C &...

We use a product call Batch Job Server, which runs dos bat files.  We get the DTS messages in our Batch Job Server logs, which is a text file for each...

put your scripts into a dts and use dtsrun in your bat file

take a look at web assistant wizard under tools.  its will walk you through creating the HTML report and scheduling the job.

I use this query for my db maintenance plan...

1. get a list of all SQL Logins and passwords, NT users and groups

2. add the SQL Logins, NT users and groups to the new server

3. get a list...

is this a fixed length file?

take a look at using dts to import your fixed length file.

have you though of using sql logins?

take a look at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;280106

use exec master..xp_logevent message,your message

We use data links for our connections and have not had any issues moving DTS from our developement server to our production server.

Our user update,insert, delete triggers are in one.  But we are using a replication package (Vision Orion/Symbiator) which generates additional triggers and we didn't want the mix our user triggers...

It could also be a space issue, the default file size is normally fairly small.  Try preallocating the file on the mainframe.