The problem lies in the For Each File Loop.  I don't see how I can implement any kind of counter without ditching my existing For Each File loop.

What if you log errors to sql (sysdtslog90 table), then you could retrieve the data based on the executionid and include in your email...  Good Luck!

Great, thats totally what I was looking for.  Thank you!

Thank you.  Unfortunately we are still on 2000 -  Hopefully by the end of the year I can start migrating our application to 2005.

Thank you for your replies.  I need to store the data in the original format in my table, any non-numeric characters are masking characters to hide certain data.  So ideally...

Here is a more accurate example:

On SERVER1 I have database DATABASE1 where there is a table IMPORTLOG with an identity field LOGID.

On SERVER2 DATABASE2 I have a view V_DATABASE1_IMPORTLOG defined as SELECT...

Thanks. The DSN entry worked for other XP clients but not for my PC, which seems to be related to how my machine was originally built.  Its a little off subject...

I have tried various things with the network admins, including DNS entries.  We can get to the default instance only, not my new named instance even using the same instance...

The old server is off line but I am already running a default instance on the new box.  Will the DNS name mapping work even when I am trying to...

Sorry, disregard my question, I just looked at sp_help_job procedure.  This should give me what I need.