Thanks for all your help Paul. I was wrong, the error was occurring in the SQL statement and another statement which can't be fixed in this manor.
So ....... Dipshit me doesn't think "Do I really need this tag at all, does it really speed up anything?" and the answer is NO. So all this time I'm trying to fix the error when the correct solution would have been just delete the tag and punt. Dumbass ----- Original Message ----- From: Paul Hill <[email protected]> To: ProFox Email List <[email protected]> Cc: Sent: Monday, October 8, 2012 2:29 PM Subject: Re: error 2066 error on a sql statement Try what I suggested: Wherethunk= "where (DEBT.STATUS="110").and.DEBT.STATUS="110".AND.Gemclien.COLLECTOR="2 ".AND.EVAL('LASTWORKED<=DATE()-15').and. gemclien.client_id=debt.clt_id .AND. GEMDEBTO.DEBTOR_ID==DEBT.DEBTOR_ID" Fox won't be able to optimise the Eval() bit. p.s. ".and." is so Clipper :-) On 8 October 2012 17:43, Michael Madigan <[email protected]> wrote: > Select acct_id, GEMDEBTO.NAME, clt_id, DEBT.Status, GEMDEBTO.INSURANCE, > GEMDEBTO.SSN,DEBT.INSURPLAN,orig_princ,princ_paid,Adj_princ,gemclien.collector; > FROM debt,GEMDEBTO,GEMCLIEN Into Cursor mikedebt; > &wherethunk > > > Wherethunk= "where > (DEBT.STATUS="110").and.DEBT.STATUS="110".AND.Gemclien.COLLECTOR="2 > ".AND.LASTWORKED<=DATE()-15.and. gemclien.client_id=debt.clt_id .AND. > GEMDEBTO.DEBTOR_ID==DEBT.DEBTOR_ID" > > > > Tag LASTWORKED is the one reporting damage > > Ignoring the tag wouldn't do much to slow the query down. > > I could also do the select without the lastworked tag and then just delete > for lastworked>date()-15 > > > > > > ----- Original Message ----- > From: Stephen Russell <[email protected]> > To: ProFox Email List <[email protected]> > Cc: > Sent: Monday, October 8, 2012 12:29 PM > Subject: Re: error 2066 error on a sql statement > > On Mon, Oct 8, 2012 at 11:12 AM, Michael Madigan <[email protected]> wrote: >> I'm getting a 2066 error on an SQL statement because one of the tags being >> used by the where clause is damaged. >> >> Is there a way to disable the SQL statement from using that particular tag? > -------------- > > Can we see some code on how you are putting the statement together as > well as the final text you are sending back? > > -- > Stephen Russell > Sr. Analyst > Ring Container Technology > Oakland TN > > 901.246-0159 cell > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CADwx0+LU=6N5mcurPpisc9OxDGZH0w=HXAVM_6NswFNwcV=n...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
