Barry,

Or you can skip this issue and have the Run Process create a "temp
record" with the attachment in it. That way the user does not care
about the physical OS that is in play and the active link could even
delete the temp record after the user gets the Attachment back to
their client too.

( Yes it requires the DB to be able to support an attachment the size
of the file. However, I think you will find that ARS does not deal
with large attachments very well too. So if that is a concern then I
would start thinking about a "LAN" or "Web server" type solution.)


--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.


On 11/30/06, Barry Lindstrom <[EMAIL PROTECTED]> wrote:
Using ARS 6.3.17 server and client, a user logs in to a load balanced
virtual server (3 servers in the environment)

The user executes a push fields activelink that triggers a filter that
fires a run process command that creates a file on whatever server they
are attached to.

IF the user fires another active link that that triggers a filter that
fires a run process command that creates another file, are we guaranteed
that both files will end up on the same server?

Barry Lindstrom
Certifiable ARJ

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to