My Action 1 and 2 were swapped...my run-if qualification
was using zTmpInt >= 0...the combination of these things were causing me to
always pull the first character off of the file name...which isn't a problem in
the native client....but due to the fact that Mid-Tier doesn't include any
path...it was in fact the cause of the issue...I won't be bugging this
one...:)
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Tuesday, May 02, 2006 7:35 AM
To: [email protected]
Subject: Re: Weird Mid-Tier Problem
Just as an FYI... I tested the code below in both an
Active Link and again in a Filter with both the Mid-Tier (patch 15) and the
Windows User tool and all 4 tests returned the same result.
I used a character field and an integer field. In the
character field I entered: C:\Program Files\AR
System\ARUSER.EXE
All 4 tests returned: ARUSER.EXE
Fred
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Friday, April 28, 2006 1:11 PM
To: [email protected]
Subject: Re: Weird Mid-Tier Problem
If you want to guarantee it runs the same from both the
UserTool and Mid-Tier convert your Active Link into a
Filter.
Filter ID 5
Run If: 'File Name' LIKE "%\%"
Action 1: Set Fields 'zTmpInt' =
STRSTR($File Name$,"\")
Action 2: Set Fields 'File Name' =
SUBSTR($File Name$, $zTmpInt$ + 1 )
Action 3: Goto 5
Fred
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of L. J. Head
Sent: Friday, April 28, 2006 12:20 PM
To: [email protected]
Subject: Weird Mid-Tier Problem
Mid-Tier 6.3 Patch 14
First off...is there a better way, secondly...does anyone
know why it's doing this
I am attaching a file to a record...and want to store the
file name in a field. Upon the file being attached I do a setfield of the
attachment field to a character field. This gives me for example
c:\autoexec.bat. I don't care about the path to the file...I just want the
file name, so I perform this set of setfields as many times as necessary to
remove all of the \'s from the file name
Setup:
2 Fields:
File Name (Character)
zTmpInt (Int)
1 Active link that fires as long as zTmpInt >= 0 (0 is
it's default value)
<ACTL> Checking AL
(5)
<ACTL> -> Passed qualification -- perform if actions
<ACTL> 0: Set Fields
<ACTL> File Name (536870916) = :\AUTOEXEC.BAT
<ACTL> 1: Set Fields
<ACTL> zTmpInt (536870917) = 1
<ACTL> 2: Goto EO
<ACTL> EO from action -- 5
<ACTL> Checking AL (5)
<ACTL> -> Passed qualification -- perform if actions
<ACTL> 0: Set Fields
<ACTL> File Name (536870916) = AUTOEXEC.BAT
<ACTL> 1: Set Fields
<ACTL> zTmpInt (536870917) = -1
<ACTL> 2: Goto EO
<ACTL> EO from action -- 5
<ACTL> Checking AL (5)
<ACTL> -> Failed qualification
<ACTL> -> Passed qualification -- perform if actions
<ACTL> 0: Set Fields
<ACTL> File Name (536870916) = :\AUTOEXEC.BAT
<ACTL> 1: Set Fields
<ACTL> zTmpInt (536870917) = 1
<ACTL> 2: Goto EO
<ACTL> EO from action -- 5
<ACTL> Checking AL (5)
<ACTL> -> Passed qualification -- perform if actions
<ACTL> 0: Set Fields
<ACTL> File Name (536870916) = AUTOEXEC.BAT
<ACTL> 1: Set Fields
<ACTL> zTmpInt (536870917) = -1
<ACTL> 2: Goto EO
<ACTL> EO from action -- 5
<ACTL> Checking AL (5)
<ACTL> -> Failed qualification
This works great and very fast on the native client....if I
however run this same workflow through Mid-Tier my file name is set to
'UTOEXEC.BAT'...it always truncates the first character of the actual file
name....your assistance is apprecated. I'm looking into upgrading to patch
16...but don't think I should need
to...
__20060125_______________________This posting was
submitted with HTML in it___ __20060125_______________________This posting was
submitted with HTML in it___ __20060125_______________________This posting was
submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
