: Ben Chernys
To: arslist@ARSLIST.ORG
Sent: Monday, September 14, 2009 4:39:37 AM
Subject: Re: Setting fields from a direct SQL...
Guys,
You don't need anything of the sort. Just issue your select and use the $1$
etc as you would if the Admin tool had figured out the number of columns
correctly
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of David Morgan
Sent: September 14, 2009 12:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Setting fields from a direct SQL...
Hi Joe, all
Whilst this may be a work-around it may be quicker than waiting for
ssage-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Joe D'Souza
Sent: 13 September 2009 22:09
To: arslist@ARSLIST.ORG
Subject: Re: Setting fields from a direct SQL...
This is a multi-part message in MIME format.
--=_NextPart_000__01CA349
om: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org]on Behalf Of LJ Longwing
Sent: Friday, September 11, 2009 7:44 PM
To: arslist@ARSLIST.ORG
Subject: Re: Setting fields from a direct SQL...
**
Joe,
I haven't tested, but your hypothesis sounds correct. I would open a
bject: Setting fields from a direct SQL...
**
Something that I had seen in the past when you use a nested function to
return a value or values where the developer client thinks it has been asked
to query for more than the requested number of columns..
I had to use one that returns a single c
Something that I had seen in the past when you use a nested function to return
a value or values where the developer client thinks it has been asked to query
for more than the requested number of columns..
I had to use one that returns a single column but the ARS somehow thinks its
more than a
6 matches
Mail list logo
