From: Ellen K. 

Doesn't solve the problem of the database privileges, and wouldn't be able
to connect to the Novell box if it's not allowed there.

Anyway I'm now just leaving myself logged in and locking the machine and
then going in on Monday morning before the other guy gets there and logging
myself out so he can log in as himself.  I'm up by then and can do it
remotely and it was easier than spending time figuring out something
better.  I'll be glad when we don't have Novell any more.

On Tue, 09 Aug 2005 13:46:30 -0500, John Cuccia 
wrote in message :

>On Tue, 09 Aug 2005 10:42:09 -0700, Ellen K.
> wrote:
>
>>On Mon, 8 Aug 2005 23:13:58 -0500, "Robert G Lewis"
>> wrote in message :
>>
>>>Why not use a script file to make the appropriate logins and
run the job ?
>>>
>>A script file, with the username and password in clear text, wonderful.
>>
>>>From a security standpoint even create a new ID strictly for
that job to use
>>>?
>>Doesn't fix the problem.  The app has to be run by someone with INSERT
>>privileges on my critical tables, not going there.
>
>You can create a dedicated account then forbid it from logging into
>any machine except the desktop running the scheduled task.

--- BBBS/NT v4.01 Flag-5