I created a dts job which is run through a vb app. The job runs fine when I run it from my machine but fails when a different user using their machine trys to run the job. I have other vb apps running dts jobs so the code I'm using is the same however I noticed the dts job, created using SQL2000, that is failing for users has my name for the owner while all the other dts jobs have a blank owner. I was able to get around the problem by creating an identical dts job using SQL 7.0 enterprise manager which saved the job with a blank owner. Any ideas on what I can do in the future when I create DTS jobs using SQL2000
Thanks.