From: Ellen K. 

There has to be a user logged on who is allowed to talk to the Novell
server, that is the whole problem.

I basically gave up on a nice solution, see my post to John C.  (I didn't
want to spend time to recompile the app in a do-nothing version to see if
it would run as me with the other guy logged on, my plate is already
overflowing right now.)

On Tue, 9 Aug 2005 14:16:29 -0500, "Robert G Lewis"
 wrote in message :

>
>"Ellen K."  wrote in message
>news:qiqhf19r51vbdt7852fgf9h8pq4p6ichjg{at}4ax.com...
>> 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.
>>
>>
>
>Have a production ( dedicated ) account with the required privileges on the
>various servers. No logon access other than the specific PC. No need to
>leave a user logged on. just leave the PC running.  This would eliminate the
>chance of someone going to that PC and using the logged on ID to access the
>networks or data. You would only need to worry about the PC going down or
>losing the connections if it occurred when the Job was running.
>
>I am making the assumptions  that you are running NT or it's successors and
>this is a controlled secure environment.
>
>Bob Lewis
>
>
>

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