[RESOLVED] Query with an asterisk(*)

stradnus

hi guys!

it seems there's lacking here in my code, if im going to use the asterisk in my query it will not display any results...

how to make the query run in php?

$sqlsalesman="select locid,location from tbllocation where locid like 'dsp*' and status=0 order by arrangement";

the query has no problem if im going to execute it in my ms access database backend.

any ideas is much appreciated. thanks.

nemonoman

Are you using MySQL? the wildcard character is the '%'

WHERE locid LIKE 'dsp%'

stradnus

nemonoman wrote:
Are you using MySQL? the wildcard character is the '%'

WHERE locid LIKE 'dsp%'

stradnus wrote:
the query has no problem if im going to execute it in my ms access database backend.

my database is ms access and the asterisk(*) is the only wildcard.

any ideas please. thanks.

Roger_Ramjet

Well, you are wrong about * being the only wildcard in Access

Character(s) in pattern Matches in expression
? or _ (underscore) Any single character
* or % Zero or more characters

Any single digit (0— 9)

[charlist] Any single character in charlist
[!charlist] Any single character not in charlist

That said, your query should work. Does it return any results when you do run it in access backend, I mean are there any rows that match that pattern? If so then post the rest of the code that executes it cos the problem could be anywhere.

stradnus

yes! the '%' is working in PHP, and it displays the output.... thanks.

I wonder why the backend MS ACCESS didnt return any results when I use the '%' as a wildcard but the '*' displayed it all. that's why i didnt use the '%' in PHP, so I tried it and it works now.

anyways, thank you for all your replies...

sidsel

stradnus wrote:
yes! the '%' is working in PHP, and it displays the output.... thanks.

I wonder why the backend MS ACCESS didnt return any results when I use the '%' as a wildcard but the '*' displayed it all. that's why i didnt use the '%' in PHP, so I tried it and it works now.

anyways, thank you for all your replies...

I have wondered about the same when playing with ms access.
Must be some M$ logic ...

Roger_Ramjet

sidsel wrote:
I have wondered about the same when playing with ms access.
Must be some M$ logic ...

More likely to be some ODBC b*******