OK, the setup is a little complicated --
I've brought my laptop into work, and I am connecting to one of our SQL Servers. Because it's my personal laptop, I'm not logged in under my network name, nor is it under the network domain; but i can still access shared network drives (it just prompts for my network id and password).
I registered the SQL Server using SQL authentication, and the username I was given was granted system administrator access. I can run DTS packages that I don't create while using the laptop. I can see all the DTS packages; I can manipulate tables - add and delete records; But I can't run (or edit) my DTS package that were created on my network computer under my network logon.
I can create a NEW DTS package, and run it no problem; just not the old ones. The old ones show the owner as cfc\tbellomo, the new ones show as WEEZ\Tim (my laptop's name, and my user account (XP Home)).
Anyone have an idea on how to remedy this? I have total access to make changes to the SQL Server if necessary.
Thanks a lot,
Timo
I've brought my laptop into work, and I am connecting to one of our SQL Servers. Because it's my personal laptop, I'm not logged in under my network name, nor is it under the network domain; but i can still access shared network drives (it just prompts for my network id and password).
I registered the SQL Server using SQL authentication, and the username I was given was granted system administrator access. I can run DTS packages that I don't create while using the laptop. I can see all the DTS packages; I can manipulate tables - add and delete records; But I can't run (or edit) my DTS package that were created on my network computer under my network logon.
I can create a NEW DTS package, and run it no problem; just not the old ones. The old ones show the owner as cfc\tbellomo, the new ones show as WEEZ\Tim (my laptop's name, and my user account (XP Home)).
Anyone have an idea on how to remedy this? I have total access to make changes to the SQL Server if necessary.
Thanks a lot,
Timo