SQL Madness

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 62603
interpreted = N
texte = Windows EXE version 6.0 Have an ODBC setup for this to MSSQL which up until now has worked wonderfully (well at least I thought so). Here is the dilemma. While trying to do a 'contains' search on any field (varchar or integer) the results are erratic when searching on anything that is number (integer) related. For example: [SQL dsn=SOMEDSN&username=SOMEUSERNAME&password=SOMEPASS &statement=SELECT * from tickets where description LIKE '%[descriptionvar]%' ORDER BY priority] [founditems] [title]
[/founditems] [/sql] Works great until you search on something like 54. So a record that has the phrase: "We ordered item number 5437. This item should be delivered promptly" In the description field (which is a varchar field) 54 Returns the proper result. However, change that search string to 543 and nothing. 5437, nothing. This is a simplistic example but I have tested this now on varchar fields and integer fields. It appears that anything over 1 or 2 chars in your search string (if they are numbers) sends back 0 results. If you search on 1 number I am getting results for records that do not even have the number in use. :_( Of course running these simple searches through query analyzer works like a charm so I am 100% certain this is a result of WebDNA communicating with MSSQL. Like I said, the interaction between the 2 has been flawless and VERY productive -- until this. Has ANYONE seen erratic results when dealing with LIKE searches and if so does anyone have any advice. I am about ready to go postal. This started as a fairly complicated search and after many hours of trying to 'fix it' reducing it to the most simple of searches showed that there is no fixing erratic results on a single variable search. Help! Alex -- Alex J McCombie Adventure Skies Interactive (ASI) Owner Box 124 888/892.6379 MartVille, NY 13111 Alex@Adventureskies.com Interface Designer WebDNA Programmer Database Designer ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
Windows EXE version 6.0 Have an ODBC setup for this to MSSQL which up until now has worked wonderfully (well at least I thought so). Here is the dilemma. While trying to do a 'contains' search on any field (varchar or integer) the results are erratic when searching on anything that is number (integer) related. For example: [SQL dsn=SOMEDSN&username=SOMEUSERNAME&password=SOMEPASS &statement=SELECT * from tickets where description LIKE '%[descriptionvar]%' ORDER BY priority] [founditems] [title]
[/founditems] [/sql] Works great until you search on something like 54. So a record that has the phrase: "We ordered item number 5437. This item should be delivered promptly" In the description field (which is a varchar field) 54 Returns the proper result. However, change that search string to 543 and nothing. 5437, nothing. This is a simplistic example but I have tested this now on varchar fields and integer fields. It appears that anything over 1 or 2 chars in your search string (if they are numbers) sends back 0 results. If you search on 1 number I am getting results for records that do not even have the number in use. :_( Of course running these simple searches through query analyzer works like a charm so I am 100% certain this is a result of WebDNA communicating with MSSQL. Like I said, the interaction between the 2 has been flawless and VERY productive -- until this. Has ANYONE seen erratic results when dealing with LIKE searches and if so does anyone have any advice. I am about ready to go postal. This started as a fairly complicated search and after many hours of trying to 'fix it' reducing it to the most simple of searches showed that there is no fixing erratic results on a single variable search. Help! Alex -- Alex J McCombie Adventure Skies Interactive (ASI) Owner Box 124 888/892.6379 MartVille, NY 13111 Alex@Adventureskies.com Interface Designer WebDNA Programmer Database Designer ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Alex McCombie

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] limit found per row (2011) FW: Rollovers (1999) Interfacing WebMerchant to www.fedex.com (1997) Gathering the values of matching fields in a database. (1998) Execute Applescript (1997) [time] math Q (2003) A little help on e-mail (HELP!!! :-) ) (1998) Trouble with formula.db + more explanation (1997) Searching for Nothing (1998) Unexpected error (1997) Convertchars Problem (2004) Re:Item options w/ price adjustment (1997) Mac: [ListFiles] bug alert (1997) [WebDNA] Search on a database (2012) [WebDNA] WebDNA 4.5.1 process DBServer.exe memory (2008) WebCat2b12--[searchstring] bug (1997) Emailer Set Up (1997) WebCatalog for guestbook ? (1997) OT-ssh help (2004) math a various prices (1997)