James, It certainly sounds like APREFIX, etc. are being lost. You can manually set these for a single value, as below:
<@VAR user$MyArray APREFIX="" ASUFFIX="" RPREFIX="" RSUFFIX="" CPREFIX="" CSUFFIX=","> Regards, Jon -----Original Message----- From: James Macfarlane [mailto:[EMAIL PROTECTED]] Sent: 16 July 2002 2:42 To: Multiple recipients of list witango-talk Subject: RE: Witango-Talk: IS IN array not working I Jon, I just used a simple assignment to create the variable: <@ASSIGN NAME="stuff" VALUE="@@resultset" SCOPE="Local"> I've had to go back in and use a loop to go through the resultset and build up the value as a string. In the search action that fil's I'm using code similar to what you mention below. The strangest thing is that this used to work, it all of a sudden started failing after months in production. - James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jon Grieve Sent: Monday, July 15, 2002 5:45 PM To: Multiple recipients of list witango-talk Subject: RE: Witango-Talk: IS IN array not working James, What does the code look like that builds/displays the comma-separated string? What I'm getting at is, if you are simply able to specify the variable name, something like... "...IS IN <@VAR local$MyArray>" ...that assumes are *not* using the default APREFIX, ASUFFIX, etc. settings. The default is to display an array as a <table>, so perhaps somewhere in the execution, your overrides are being lost. Just my 2p... Jon -----Original Message----- From: James Macfarlane [mailto:[EMAIL PROTECTED]] Sent: 15 July 2002 22:19 To: Multiple recipients of list witango-talk Subject: Witango-Talk: IS IN array not working For the last few weeks we've been having a strange problem where a search action that uses IS IN function gives us an error even though the code hasn't changed. After dumping out the <@SQL> statement to the browser it seems that the array used in the IS IN is coming back as an HTML table of values, rather than an array. We've even had a query with three IS IN functions fail -- the first IS IN showed a string of comma-separated values (what you'd expect), but the other two arrays appeared as HTML tables. This is driving us nuts! HELP! - James. ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
