SQL Madness

This WebDNA talk-list message is from

2005

It keeps the original formatting. numero = 62603
interpreted = N
texte = Windows EXE version 6.0Have an ODBC setup for this to MSSQL which up until now has workedwonderfully (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 thatis number (integer) related.For example:[SQL dsn=SOMEDSN&username=SOMEUSERNAME&password=SOMEPASS&statement=SELECT * from tickets wheredescription 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 andnothing. 5437, nothing.This is a simplistic example but I have tested this now on varchar fieldsand integer fields. It appears that anything over 1 or 2 chars in yoursearch string (if they are numbers) sends back 0 results. If you search on 1number I am getting results for records that do not even have the number inuse. :_(Of course running these simple searches through query analyzer works like acharm so I am 100% certain this is a result of WebDNA communicating withMSSQL. Like I said, the interaction between the 2 has been flawless and VERYproductive -- until this.Has ANYONE seen erratic results when dealing with LIKE searches and if sodoes anyone have any advice. I am about ready to go postal. This started asa 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 fixingerratic results on a single variable search.Help!Alex-- Alex J McCombie Adventure Skies Interactive (ASI)Owner Box 124888/892.6379 MartVille, NY 13111Alex@Adventureskies.comInterface 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:

Re: SQL Madness ( Alex McCombie 2005) Re: SQL Madness ( "Scott Anderson" 2005) Re: SQL Madness ( Alex McCombie 2005) Re: SQL Madness ( Jesse Proudman 2005) Re: SQL Madness ( "Scott Anderson" 2005) SQL Madness ( Alex McCombie 2005) SQL Madness ( Alex McCombie 2005)

Windows EXE version 6.0Have an ODBC setup for this to MSSQL which up until now has workedwonderfully (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 thatis number (integer) related.For example:[SQL dsn=SOMEDSN&username=SOMEUSERNAME&password=SOMEPASS&statement=SELECT * from tickets wheredescription 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 andnothing. 5437, nothing.This is a simplistic example but I have tested this now on varchar fieldsand integer fields. It appears that anything over 1 or 2 chars in yoursearch string (if they are numbers) sends back 0 results. If you search on 1number I am getting results for records that do not even have the number inuse. :_(Of course running these simple searches through query analyzer works like acharm so I am 100% certain this is a result of WebDNA communicating withMSSQL. Like I said, the interaction between the 2 has been flawless and VERYproductive -- until this.Has ANYONE seen erratic results when dealing with LIKE searches and if sodoes anyone have any advice. I am about ready to go postal. This started asa 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 fixingerratic results on a single variable search.Help!Alex-- Alex J McCombie Adventure Skies Interactive (ASI)Owner Box 124888/892.6379 MartVille, NY 13111Alex@Adventureskies.comInterface 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:

MacAuthorize order data fields WAS:How To question... (1997) Windows XP and cookies (2004) Location of Webcat site in folder hierarchy (1997) OT JavaScript question (1999) Problems with [Applescript] (1997) help testing quicktime delivery (1997) PSC recommends what date format yr 2000??? (1997) searching multiple databases (1997) WCS Newbie question (1997) Cart Question (1998) WebDNA 5.0 Questions (2003) Help! WebCat2 bug (1997) WebCatalog for Mac 2.0.1 Released (1997) So .. How fast (2003) Cobalt RaQ (2000) I have observed and I am gone. (1998) Where's Cart Created ? (1997) Is [upload] avail. in 3.0.8 for NT? (2000) ASCII Code 127 (2004) [searchString] (1997)