Steve,

try single quotes around the userref

B2.B_ShopperID='DB4AA3C73D29620D3E3E8E61'

-----Original Message-----
From: Fogelson, Steve <[EMAIL PROTECTED]>
To: Witango User Group (E-mail) <[EMAIL PROTECTED]>
Date: Monday, February 03, 2003 10:09 AM
Subject: Witango-Talk: Query problem


>I am using a Win2K server running R:Tango 2000 with R:Base 6.5.
>
>I made a change in my shopping cart this morning and created a problem.
>
>I changed the shopper id field in my basket table from an integer to a text
>field with length of 30 characters. I wanted to set the shopper id to
>_UserReference in cases when a shopper doesn't login.
>
>I copied the fresh database over and made the appropriate software
>modifications, but I get the following error:
>
>[Query] [83] SELECT
>P1.P_ID,P1.P_SKU,P1.P_Name,P1.P_Price,B2.B_ItemNumber,B2.B_Quantity,P1.P_SK
U
>As ReferenceNumber,P1.P_Price AS Tax,P1.P_Price AS CurrentPrice FROM
>Products P1,Basket B2 WHERE (B2.B_ShopperID=DB4AA3C73D29620D3E3E8E61 AND
>P1.P_Disable IS NULL) AND ((P1.P_ID=B2.P_ID)) ORDER BY 5 ASC
>[Error] [83] 2367 [RBTI][Oterro ODBC Driver][Catalog]-ERROR- Syntax error
>(2367) 37000
>[Error] [83] -101 General error during data source operation.
>[Error] [383] [Microsoft][ODBC Driver Manager] Function sequence error
S1010
>
>If I remove the B_ShopperID from the criteria of the search, no error, but
>obviously wrong results. Is there something wrong with setting the id to
the
>user reference? I do have B_ShopperID set up as a primary key. Wouldn't
>think that would cause a problem.
>
>Any other ideas?
>
>Steve Fogelson
>Internet Commerce Solutions
>________________________________________________________________________
>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

Reply via email to