Thanks Jason, and for anyone else looking at this. I've been talking with Phil Wade and he suggested the same thing. Did the upgrade and still have the same problem. Phill will be looking into this issue on Monday.
Thanks for your help! -----Original Message----- From: Jason Pamental [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 9:53 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Possible Search action bug? Gene, I haven't heard of this issue, but the first thing you should do is download the latest dev studio installer, which has been up to 037 for a while. You can get it from Witango's site or any of the other distributor/reseller sites like ours (http://witango.us/downloads - short registration required) Jason On Friday, April 4, 2003, at 08:29 AM, Wolf, Gene wrote: > I'm wondering if anyone else has run into this or whether Witango > was > supposed to do this to begin with. First, I'm using Witango 5 .0.1.035 > Development Studio on Windows 2000 Professional. What I wanted to do > is set > up a seach action with criteria similar to the following logic: IF > (case1) > AND (case2 or case3) then retrieve the records from the database > matching > the criteria. > > Well, I thought that right clicking and Inserting Criteria Seperator > would allow me to specify just that kind of logic. When I set it up, > close > the seach action and open it back up the criteria line I entered is > gone and > all of the criteria tests have been changed to AND's. > Dropping the search action into the SQL window shows the following: > > SELECT P1.PgmMgr,P1.Pgm FROM dbo.ProgramActionEmail P1 WHERE > (P1.PgmMgr='2496' AND P1.Pgm='pro-iii'P1.Pgm='ADP') > > Note that that the SQL command is malformed. This is not a typo. I've > copied > it directly from the SQL Query window. > > Now, if I open the search window once more, and then simply close it > and > drag the search action into the SQL Query window again I get the > following > SQL generated: > > SELECT P1.PgmMgr,P1.Pgm FROM dbo.ProgramActionEmail P1 WHERE > (P1.PgmMgr='2496' AND P1.Pgm='pro-iii' AND P1.Pgm='ADP') > > This is valid SQL. > > My question is, first, can anyone else confirm this is also happening > to > them, second, can they get the criteria seperator to work for them and > 3 is > there a way to specify in the search action the logic I want without > having > to resort to a Direct DBMS, which I'm doing now to get around this > situation? > > Thanks for any help! > > Gene Wolf > Business Systems Analyst > DRS Optronics, Inc. > 2330 Commerce Park Drive > Palm Bay, Florida 32905 > Phone: 321-309-0685 > E-mail: [EMAIL PROTECTED] > > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > -- ____________________________________________________________________ Jason Pamental, President [EMAIL PROTECTED] Bathysphere Digital Media Services, Inc. http://bathyspheredms.com ____________________________________________________________________ Tel: 401.490.6830 Fax: 401.490.6831 ________________________________________ A North American Distributor for Witango (http://www.witango.us) Rapid Web Application Development - XML Execution Engine ________________________________________________________________________ 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
