Re: Witango-Talk: IS IN screws up

[Atrix Wolfe]

the problem is that arrays have things called:   aPrefix  - whats shown before an array aSuffix  - whats shown after an array   cPrefix  - whats shown before a column cSuffix  - whats shown after a column   rPrefix  - whats shown before a row rSuffix  - whats shown after a row   check them out in the docs...they are the reason why when you say:   @@Local$resultset   it shows up as a table...you can use the <@var> tag to set these to different values, to for instance make a list seperated by commas.  You do that by setting all to '' (blank) and set cSuffix to ',' (comma) and then removing the last character from that string because it will put a comma at the end of your string. ----- Original Message ----- From: James MacFarlane To: Multiple recipients of list witango-talk Sent: Friday, December 06, 2002 11:58 AM Subject: Witango-Talk: IS IN screws up Every once in a while I go to use a query action that uses and IS IN clause like this:   SELECT M1.planVariantId FROM dbo.MassPriceLookup M1 WHERE (M1.priceGroupId=1 AND M1.VariantId in (11,11,2,2,3,3,30)   Get a syntax error, so I have the application dump out the SQL statement and it looks like this:   SELECT M1.planVariantId FROM dbo.MassPriceLookup M1 WHERE (M1.priceGroupId=1 AND M1.VariantId in ( 11 11 2 2 3 3 30 )   So instead of dumping in comma-separated values, it puts in the HTML table of values. Why?!?!?!   I�ve included my screenshot of the query         ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body