FP 2003 Database Results Error

[gandy]

I upgraded to FP 2003 from 2002

I have been able to begin updating my pages with some of 2003 new stuff but a problem has occurred

On all of the .asp on which i display database results I get the following error

Database Results Wizard Erro
The operation failed. If this continues, please contact your server administrator.

This error messages has occurred throughout my site although I have only worked on one or two pages with FP2003

Can anyone tell me how to get my database results pages to work again?

 

[Kathleen Anderson [MVP - FP]]

Edit the file fpdbrgn1.inc (in the _fpclass folder) and set fp_DEBUG = True
and then try again and tell us what the error message is.

 

[gandy]

Is this something that My host should do? I cannot find the folder you referred to in your Message.

----- Kathleen Anderson [MVP - FP] wrote: -----

Edit the file fpdbrgn1.inc (in the _fpclass folder) and set fp_DEBUG = True
and then try again and tell us what the error message is.


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

I upgraded to FP 2003 from 2002.

I have been able to begin updating my pages with some of 2003 new

stuff but a problem has occurred.

 

[Kathleen Anderson [MVP - FP]]

You should be able to do this on either your local site or your live site.
The _fpclass is a hidden folder, to see it, go to Tools | Site Settings |
Advanced and check the box that says "Show hidden files and folders".

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

Is this something that My host should do? I cannot find the folder
you referred to in your Message.

----- Kathleen Anderson [MVP - FP] wrote: -----

Edit the file fpdbrgn1.inc (in the _fpclass folder) and set
fp_DEBUG = True and then try again and tell us what the error
message is.


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

I upgraded to FP 2003 from 2002.

 

[gandy]

Ok, i made the change to the file as suggested. Now I get the following error

Database Results Wizard Erro
Your page contains a query with user input parameters that could not be resolved
This could happen if your DatabaseRegionStart webbot has an empty or missing s-columnnames or s-columntypes attributes
You may need to read Microsoft Knowledge Base Article 817029.

 

[Kathleen Anderson [MVP - FP]]

gandy:
Please don't snip - it makes the conversation difficult to follow.

Can you post your SQL?

Did you create this database in FrontPage (with Save to Database form) or
did you create it with Access?

 

[Gandy]

The following is a copy of the SQL

SELECT imageurl,price,producturl,productname,small_banner,impressionurl FROM Visions WHERE (Product_Keywords LIKE '%:roduct_Keywords::%') and productname NOT LIKE '%plaid corry%' and product_keywords NOT LIKE '%pets%' and productname NOT LIKE '%green corry%' and product_keywords NOT LIKE '%bedding%

This is an Access database .mdb file. These database files and results pages worked fine yesterday before I started using FP2003.

 

[Kathleen Anderson [MVP - FP]]

Gandy:

"Don't snip" means leave the entire message in that you are replying to.

What happens if you try a create a new query page in this web (instead of
changing an existing page)?

 

[Gandy]

I tried to create a new results page in the same web and get the same error message as follows

Database Results Wizard Erro
Your page contains a query with user input parameters that could not be resolved
This could happen if your DatabaseRegionStart webbot has an empty or missing s-columnnames or s-columntypes attributes
You may need to read Microsoft Knowledge Base Article 817029

One or more form fields were empty. You should provide default values for all form fields that are used in the query

I apologizes for snipping. Im still not quite sure what snipping is, but please dont over load me.

 

[gandy]

I figured out snipping, Sorr
----- Kathleen Anderson [MVP - FP] wrote: ----

Gandy

"Don't snip" means leave the entire message in that you are replying to

What happens if you try a create a new query page in this web (instead o
changing an existing page)

 

[Kathleen Anderson [MVP - FP]]

Great!!

How big is your database? Can you zip it up (Winzip) and send it to me by
email?


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

I figured out snipping, Sorry
----- Kathleen Anderson [MVP - FP] wrote: -----

Gandy:

"Don't snip" means leave the entire message in that you are
replying to.

What happens if you try a create a new query page in this web
(instead of changing an existing page)?


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

The following is a copy of the SQL:

imageurl,price,producturl,productname,small_banner,impressionurl
FROM > Visions WHERE (Product_Keywords LIKE
'%:roduct_Keywords::%') and > productname NOT LIKE '%plaid
corry%' and product_keywords NOT LIKE > '%pets%' and productname
NOT LIKE '%green corry%' and > product_keywords NOT LIKE
'%bedding%' >> This is an Access database .mdb file. These
database files and > results pages worked fine yesterday before I
started using FP2003.

 

[gandy]

I just took a look at the database and there is nothing unusual. It consists of a simple flat table with columns and rows. The field names are the same today as they were yesterday. Again, they worked fine earlier.

----- Kathleen Anderson [MVP - FP] wrote: -----

Great!!

How big is your database? Can you zip it up (Winzip) and send it to me by
email?


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

I figured out snipping, Sorry
----- Kathleen Anderson [MVP - FP] wrote: -----

Gandy:
"Don't snip" means leave the entire message in that you are replying to.
What happens if you try a create a new query page in this web

(instead of changing an existing page)?~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
http://www.spiderwebwoman.com/resources/

The following is a copy of the SQL:

FROM > Visions WHERE (Product_Keywords LIKE
'%:roduct_Keywords::%') and > productname NOT LIKE '%plaid
corry%' and product_keywords NOT LIKE > '%pets%' and productname
NOT LIKE '%green corry%' and > product_keywords NOT LIKE
'%bedding%' >> This is an Access database .mdb file. These
database files and > results pages worked fine yesterday before I
started using FP2003.

 

[gandy]

I just uploaded a fresh copy of my .mdb file, and I continue to get the error message. So the .mdb files are valid. Some other setting has changed that is causing the error. Any help would be appreciated.

----- gandy wrote: -----

I just took a look at the database and there is nothing unusual. It consists of a simple flat table with columns and rows. The field names are the same today as they were yesterday. Again, they worked fine earlier.

----- Kathleen Anderson [MVP - FP] wrote: -----

Great!!

How big is your database? Can you zip it up (Winzip) and send it to me by
email?


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

I figured out snipping, Sorry
----- Kathleen Anderson [MVP - FP] wrote: -----

Gandy:
"Don't snip" means leave the entire message in that you are replying to.
What happens if you try a create a new query page in this web

(instead of changing an existing page)?~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
http://www.spiderwebwoman.com/resources/

The following is a copy of the SQL:

FROM > Visions WHERE (Product_Keywords LIKE
'%:roduct_Keywords::%') and > productname NOT LIKE '%plaid
corry%' and product_keywords NOT LIKE > '%pets%' and productname
NOT LIKE '%green corry%' and > product_keywords NOT LIKE
'%bedding%' >> This is an Access database .mdb file. These
database files and > results pages worked fine yesterday before I
started using FP2003.

 

[Jeff McClellan]

I had the same problem. I just upgraded from 2002 to 2003 and started
getting the same message.

Make sure the database field names in your SQL statement are the same case
as they are in your access database. I know that sounds too simple but it
worked for me.

BEFORE:
fp_sQry="SELECT [IndividualResultsCrosstab].* FROM
[IndividualResultsCrosstab] where swimmer = '::swimmer::'"
AFTER:
fp_sQry="SELECT [IndividualResultsCrosstab].* FROM
[IndividualResultsCrosstab] where Swimmer = '::swimmer::'"


Jeff

I just uploaded a fresh copy of my .mdb file, and I continue to get the

error message. So the .mdb files are valid. Some other setting has changed
that is causing the error. Any help would be appreciated.

----- gandy wrote: -----

I just took a look at the database and there is nothing unusual. It

consists of a simple flat table with columns and rows. The field names are
the same today as they were yesterday. Again, they worked fine earlier.

----- Kathleen Anderson [MVP - FP] wrote: -----

Great!!

How big is your database? Can you zip it up (Winzip) and send it to me by
email?


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

I figured out snipping, Sorry
----- Kathleen Anderson [MVP - FP] wrote: -----

Gandy:
"Don't snip" means leave the entire message in that you

are
replying to.

What happens if you try a create a new query page in

this web
(instead of changing an existing page)?

--

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

The following is a copy of the SQL:
SELECT

imageurl,price,producturl,productname,small_banner,impressionurl
FROM > Visions WHERE (Product_Keywords LIKE
'%:roduct_Keywords::%') and > productname NOT LIKE '%plaid
corry%' and product_keywords NOT LIKE > '%pets%' and productname
NOT LIKE '%green corry%' and > product_keywords NOT LIKE
'%bedding%' >> This is an Access database .mdb file. These
database files and > results pages worked fine yesterday before I
started using FP2003.

 

[John Jansen \(MSFT\)]

Check the other post you have on this:

When the custom query is done on the update page that sends the change to
the database, it doesn't seem to include the field names and attributes in
the database region of the page. On the update page, look for "<!--webbot
bot="DatabaseRegionStart" s-columnnames s-columntypes" in the code view of
the update page and add the names of the two fields referenced in the query
and the appropriate code for the type of field it is. For example:

s-columnnames="PART_NO,PRICE" s-columntypes="202,202"

I have two fields here, and both are set up as text fields in the DB (202.)
Other codes are 3 for numeric, 135 for dates, 203 for memo (I think.) So if
I decide to use a numeric field for price, it should be:

s-columnnames="PART_NO,PRICE" s-columntypes="202,3"

--
Thanks!
John Jansen
Microsoft Office FrontPage
This posting is provided "AS IS" with no warranties, and confers no rights.

I just uploaded a fresh copy of my .mdb file, and I continue to get the

error message. So the .mdb files are valid. Some other setting has changed
that is causing the error. Any help would be appreciated.

----- gandy wrote: -----

I just took a look at the database and there is nothing unusual. It

consists of a simple flat table with columns and rows. The field names are
the same today as they were yesterday. Again, they worked fine earlier.

----- Kathleen Anderson [MVP - FP] wrote: -----

Great!!

How big is your database? Can you zip it up (Winzip) and send it to me by
email?


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

I figured out snipping, Sorry
----- Kathleen Anderson [MVP - FP] wrote: -----

Gandy:
"Don't snip" means leave the entire message in that you

are
replying to.

What happens if you try a create a new query page in

this web
(instead of changing an existing page)?

--

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

The following is a copy of the SQL:
SELECT

imageurl,price,producturl,productname,small_banner,impressionurl
FROM > Visions WHERE (Product_Keywords LIKE
'%:roduct_Keywords::%') and > productname NOT LIKE '%plaid
corry%' and product_keywords NOT LIKE > '%pets%' and productname
NOT LIKE '%green corry%' and > product_keywords NOT LIKE
'%bedding%' >> This is an Access database .mdb file. These
database files and > results pages worked fine yesterday before I
started using FP2003.