Hi
Romanus,
Thank you for the answer.
Using the Run As option, it forces to specific a user account and the pwd, which would be difficult to handle because of security reason and number of PC to be handled.
Is there any option which would run the package under logged user's session? Leaving the Run As field blank, the package is then deployed with system account, so is there any specific parameter which does the same job with logged user's account without using the pwd?
Thanks in advance for your reply
Sutha