A
Alittleconfused
I hate to bug you guys again, but I've done everything I can think of to try
and resolve my problem on my own, without much success. So here's the deal:
I connected my access database to my website, and everything seems to be
alright. I've added a web component search box, and the "start search" and
"reset" buttons work just fine. But the database results region appears with
yellow text on my published site as: "Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator."
And when I put in a search just for the sake of it, I get a new page that
says:
Cannot run the FrontPage Server Extensions on this page:
"http://www.thomsonequipment.com/Searchpg.asp"
Is there something I'm missing about making that page part of the group??
My host supports FP extensions, and so far they've been working. And my
search page is .asp I read that sometimes default values have to be set in
numeric and autonumber fields, so I did that, and it's still not working.
ANY suggestions would be GREATLY appreciated. Thanks so much.
and resolve my problem on my own, without much success. So here's the deal:
I connected my access database to my website, and everything seems to be
alright. I've added a web component search box, and the "start search" and
"reset" buttons work just fine. But the database results region appears with
yellow text on my published site as: "Database Results Wizard Error
The operation failed. If this continues, please contact your server
administrator."
And when I put in a search just for the sake of it, I get a new page that
says:
Cannot run the FrontPage Server Extensions on this page:
"http://www.thomsonequipment.com/Searchpg.asp"
Is there something I'm missing about making that page part of the group??
My host supports FP extensions, and so far they've been working. And my
search page is .asp I read that sometimes default values have to be set in
numeric and autonumber fields, so I did that, and it's still not working.
ANY suggestions would be GREATLY appreciated. Thanks so much.