Keeping A VB.NET Connection Open Through Multiple STRPCCMD Calls

[Skittle]

I have been experimenting with STRPCO and STRPCCMD for the first time. I want to users to be able to call a VB.Net executable on thier PC's by hitting a function key on a green screen. The VB.Net program will then talk back to the AS400 via an OLEDB connection to perform a few tasks.

The problem I have is that each time the user calls the VB.Net program, it will need to open a new connection to the AS400 and trigger a request for a username and password.
Since users will be using this program throughout the day,I need the program to use authenticate only the first time.

Anybody any idea how I can get multiple calls of the VB.net program using the same connection/authentication over and over automatically? I seem to remember achieving this by accident wwith VB6 many years ago but I can't remember how.




Dazed and confused.

Remember.. 'Depression is just anger without enthusiasum'.

 

[Mercury2]

Don't use STRPCO/STRPCCMD which is nowadays an old technology with the awkward constraint to install the VB.Net app on each user's PC. I'd put the VB.Net app in a serve r shared folder and use RUNRMTCMD instead.

Philippe