N
Nicholas
I have an mdb database generated by FP2000 where I want to
have a search form search a field called Headline. Here is
the query in the FP asp.
fp_sQry="SELECT * FROM Results WHERE (Headline
= '::Headline::')"
With the search form there, this setup will not return any
records ever, either through the form or through an ASP
generated drop down I have. Taking the drop down out makes
no difference.
If I remove the search form, it returns all of the records
on loading as a result (I guess) of this query:
fp_sQry="SELECT * FROM Results"
The search form and drop down don't have any effect: it
returns all of the records when the page reloads.
I'm pulling my hair out as I have a different database set
up almost exactly the same way that works fine. The only
major difference between them is that the one that doesn't
work has 42 columns or fields total versus 13 in the one
that works.
Is the mdb corrupted or has errors, maybe? I don't have
Access to open it.
have a search form search a field called Headline. Here is
the query in the FP asp.
fp_sQry="SELECT * FROM Results WHERE (Headline
= '::Headline::')"
With the search form there, this setup will not return any
records ever, either through the form or through an ASP
generated drop down I have. Taking the drop down out makes
no difference.
If I remove the search form, it returns all of the records
on loading as a result (I guess) of this query:
fp_sQry="SELECT * FROM Results"
The search form and drop down don't have any effect: it
returns all of the records when the page reloads.
I'm pulling my hair out as I have a different database set
up almost exactly the same way that works fine. The only
major difference between them is that the one that doesn't
work has 42 columns or fields total versus 13 in the one
that works.
Is the mdb corrupted or has errors, maybe? I don't have
Access to open it.