Can't search some DB columns

[Nichcolas]

I used FP 2000 to create an Access DB, a connection, and
DRW results. Then I created a different db by importing
data from Excel, gave it the same column names and saved
it over the .mdb created by FP.

This is a very simple Name, Address, City, State, Zip,
Telephone database with two tables for two cities. All of
the columns are Access text fields (except for the ID of
course).

The only DRW search forms that returns results are City
and Zip. And even these only return results if you enter
an exact term, even though I specified LIKE. I've tried it
every which way. Searching the name, address, state or
phone fields will only get "No Records Returned".

Has anybody seen this and can help?!

 

[Nicholas]

Sort of found my own answer. The problem is in the Access
DB and not anything in Front Page.

Have to use ='*' & userinput & '*' in the SQL statement
instead of LIKE userinput

But I have other databases (created by FP) where LIKE
userinput works fine. Why the difference? Guess I'll ask
in an Access forum.

 

[Kathleen Anderson [MVP - FrontPage]]

Hi Nicholas:
You may want to take a look at
Description of the SQL syntax that is generated by the FrontPage Database
Results Wizard
http://support.microsoft.com/default.aspx?scid=kb;[LN];306430

 

[Nicholas]

Thanks. The lack of % symbols around the text input might
be the problem. It's just treating LIKE the same as = even
in the queries written in Access.

-----Original Message-----
Hi Nicholas:
You may want to take a look at
Description of the SQL syntax that is generated by the FrontPage Database
Results Wizard
http://support.microsoft.com/default.aspx?scid=kb; [LN];306430

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
http://www.spiderwebwoman.com/resources/

Sort of found my own answer. The problem is in the Access
DB and not anything in Front Page.

Have to use ='*' & userinput & '*' in the SQL statement
instead of LIKE userinput

But I have other databases (created by FP) where LIKE
userinput works fine. Why the difference? Guess I'll ask
in an Access forum.

.