Database Results Wizard Error - Frontpage 2003 (Full Version)

All Forums >> [Web Development] >> ASP and Database



Message

Spooky -> Database Results Wizard Error - Frontpage 2003 (4/8/2002 0:00:00)

quote:

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


The FP2003 code has changed slightly. To see the true error, open the hidden folder /_fpclass/ and edit the fpdbrgn1.inc file

At about line 19, change :

fp_DEBUG = False

to :

fp_DEBUG = True



cfreema7 -> RE: DRW Error - 2003 (2/25/2004 7:02:13)

Spooky,

It still doesnt work, see response > http://www.frontpagewebmaster.com/m-182854/tm.htm

Chris



cfreema7 -> RE: DRW Error - 2003 (2/25/2004 7:42:27)

Spooky,

Microsoft lists this as a cure: http://support.microsoft.com/default.aspx?scid=kb;en-us;828905&Product=fp2003

But I still can't get it to work.

chris



Spooky -> RE: DRW Error - 2003 (2/25/2004 8:22:00)

Its not designed to fix the error, just show the actual problem.
Yours doesnt show the problem when changed?

http://www.frontpagewebmaster.com/m-182839/tm.htm

Or, the recommended 'easy' fix is to replace the includes in the '_fpclass' folder with the olde versions from FP2000/2



Spooky -> RE: DRW Error - 2003 (3/20/2004 21:06:34)

http://support.microsoft.com/?id=817029

Work around:
==========
The workaround is to manually update the s-columnnames and s-columntypes values in the DatabaseRegionStart webbot code.
To do so, us the following steps:

1. Create a new 'default' Database Results Wizard page with the same table
as in the page giving the error.

2. Switch to HTML view.

3. Locate the following section of code:
<!--webbot bot="DatabaseRegionStart"

4. Copy the following text of s-columnname and s-columntype [example given
below].
s-columnnames="Expr1000,EmployeeID,FirstName" s-columntypes="3,3,202"

5. Open the page that is returning the error in FrontPage 2003.

6. Switch to the HTML view and locate the following section of code:
<!--webbot bot="DatabaseRegionStart"

7. Update the s-columnnames value to include all field names, including derived names for fields from aggregate functions like COUNT, etc. For example:
s-columnnames="Expr1000,EmployeeID,FirstName"

8. Update the s-columntypes value to include all field types, including derived types from aggregate functions like COUNT, etc. For example:
s-columntypes="3,3,202"



gb_jones -> RE: DRW Error - 2003 (4/30/2004 13:14:04)

Hi, Spooky. I took your advice about changing the fpdbrgh1.inc file, and that
showed me some good detail... it also pointed me to a knowledge base article
that basicly said upgrade to .NET... not what I want to do. I read your further
reply, and all I can say is, "HUH????" My databaseregion fp code is:

<!--webbot bot="DatabaseRegionStart" s-columnnames s-columntypes
s-dataconnection="RT" b-tableformat="TRUE" b-menuformat="FALSE"
s-menuchoice s-menuvalue b-tableborder="TRUE" b-tableexpand="TRUE"
b-tableheader="TRUE" b-listlabels="TRUE" b-listseparator="TRUE"
i-listformat="0" b-makeform="FALSE" s-recordsource s-displaycolumns
s-criteria s-order s-sql="UPDATE respondent
SET lname='::lname::',fname='::fname::',phone='::phone::',wphone='::wphone::',
email='::email::',address='::address::',city='::city::',state='::state::',zip='::zip::'
WHERE recordid=Request.Form("recordid")"
b-procedure="FALSE" clientside suggestedext="asp"
s-defaultfields="lname=&fname=&phone=&wphone=& email=&address=&city=&state=&zip="
s-norecordsfound="Record Updated" i-maxrecords="0" i-groupsize="0" botid="0"
u-dblib="_fpclass/fpdblib.inc" u-dbrgn1="_fpclass/fpdbrgn1.inc"
u-dbrgn2="_fpclass/fpdbrgn2.inc" tag="TBODY" preview="
<tr>
<td colspan=64 bgcolor="#FFFF00" width="100%">
<font color="#000000">This is the start of a Database Results region.</font></td></tr>
" b-UseDotNET="FALSE" CurrentExt sa-InputTypes b-DataGridFormat="FALSE"
b-DGridAlternate="TRUE" sa-CritTypes b-WasTableFormat="TRUE" startspan -->
<!--#include file="_fpclass/fpdblib.inc"-->


I'm able to make SOME sense out of all that, but the s-columnames stuff left me in the dust.....
Where does one find information on what the s-columntypes values are?



tgorski -> RE: DRW Error - 2003 (5/6/2004 10:25:42)

quote:

Database Results Wizard Error

As always, YOU ROCK SPOOKY!

This problem was driving me nuts for days while I attempted using Microsoft suggested fixes.

I used your "easy fix" (replacing the _fpclass files), and BINGO!

Someday I'll learn the lesson to ALWAYS check here FIRST, BEFORE going to microsoft!

One question: The "easy fix" is not always the preferred solution, because of possible side effects. Are there any I should anticipate in this situation? I'm the only one using FP2003 in my office, so I'm also confused as to why the _fpclass files got changed in the first place.

Thanks again.



sduraybito -> RE: DRW Error - 2003 (5/10/2004 12:19:10)

Just wanted to update my experience.

I first started having problems with this a while back and dutifully went ahead and made sure s-columnname and s-columntype was in all my code. This worked fine until I discovered my SortColumn tables weren't working. The reason is because there's no SortColumn field in my database.

The only workaround I've come up with is pulling in the old _fpclass files and naming them fpdb(x)old. Now I have six files in my _fpclass folder (three new, three old). Everything seems to work OK.

Spooky, can you conjecture where MS is taking us with this sudden code change? I'm on FP 2002 still, but I suspect my fpclass files were changed to FP2003 status during a recent Windows Update. Is this part of MS security initiative and what is its purpose?

Peter



kdp -> RE: DRW Error - 2003 (5/10/2004 13:34:40)

Thanks spooky the 'easy' fix worked for me. The only problem is if I modify any asp page, the class files are updated to 2002. This makes is very difficult during testing. My question is what's the answer. Upgrade to 2003 or stay at 2000, and I'd love to hear the answer to sduraybito's question "Where is MS taking us"?



ttjager -> RE: DRW Error - 2003 (5/12/2004 20:17:30)

Just a quick note. After changed the debug parameter from False to True, all I had to do (in most cases) was open the pages containing a DRW region and simply click save. FP2002 did whatever magic was required and everything started working again. Go figure.

Todd



evansforsyth -> RE: DRW Error - 2003 (6/15/2004 3:09:40)

I need some advice! Will an upgrade to 2003 provide a reliable fix? This problem is driving me crazy!

Sounds like even in 2003 it will keep reoccuring. Please tell me it isn't so!

Evans



BeTheBall -> RE: DRW Error - 2003 (6/15/2004 13:11:16)

Evans, I was not even aware this problem occurred in FP 2002 until recently. The problem really showed up shortly after the release of FP 2003. So in short, no an upgrade will not ease your pain. I still use FP 2000 and sincerely doubt I will change unless a solid solution to this problem is found. I can't say this for sure, but I think there is also a correlation with Server 2003. It seems, at least in some instances, that users had FP 2002 pages that worked fine until the host upgraded to Server 2003.



evansforsyth -> RE: DRW Error - 2003 (6/15/2004 13:25:24)

Thanks for your advice!

In my case I suspect a MicroSoft update to Office 2002--believe it was called SR3.

I'm considering moving to DreamWeaver or using CodeCharge. Can't believe MS has been so irresponsible.

Evans



evansforsyth -> RE: DRW Error - 2003 (6/16/2004 11:43:55)

OK, here goes. It is now working for me; my guess is.

We installed a 2002 to 2003 update into a SEPARATE directory.

Now, when an asp page is changed, that pesky FPDBRGN1.INC file (in _fpclass) works!

---------------------------------------------

Pure speculation, but maybe:
- earlier, when the SR3 Office update was completed, it led to a "bad" FPDBRGN1.INC file being used whenever an asp page was changed. (SR3 may be only one of many ways MicroSoft gives us this problem.)

and

- after installing 2003 in the same directory, without removing 2002, the program continued to use the "bad" FPDBRGN1.INC. (By default, if you decide to keep the old version--the new version goes into the old directory. ??Hence the problem??)

- once the two versions were segregated into separate directories the new, "improved" FPDBRGN1.INC got used instead.

Pure speculation--but if it continues to work!!

Evans



BobGeezer -> RE: DRW Error - 2003 (7/9/2004 14:23:12)

I tried the fix involving replacing the includes, but now DWR won't even produce a simple retrieval . . nothing happens at all. The s-columnnames and types code is OK, but no cigar. Do I also have to change the DEBUG parameter? That should just be informational, not production, no?

I guess it's back to FP 2000 for me



BobGeezer -> RE: DRW Error - 2003 (9/25/2004 19:57:38)

Is there any new news about this error? Is MS doning anything? I went back to FP2000, but it still won't do any updates to DB.s This is applications that have run for at least 5 yeaars without error.

THese are production sites that I MUST get running again. . .what would you do?



BobGeezer -> RE: DRW Error - 2003 (9/25/2004 20:00:09)

I notice you said you are still using FP2000. I went back to it after FP2003 was such a dog, but now my old production sites don't work (won't update a table) either !!

What would you do?



dvdc3079 -> RE: DRW Error - 2003 (10/2/2004 11:42:06)

I recently experienced this problem. I am using FP2003 with MS Access 2000. I checked the s-columnnames and s-columntypes and couldn't find anything wrong. I then changed the debug from false to true and started getting a newer message about invalid path. After some trial and error, I found that FP was setting my connection string in the Global.asa file to:

Application("Database1_ConnectionString") = "DRIVER={Microsoft Access Driver (*.mdb)};DBQ=URL=fpdb/cfa.mdb".

If I put a slash in front of the fpdb so that it reads DBQ=URL=/fpdb/cfa.mdb" then everything starts working again. I can't say that your problem is similar but you might try it. One drawback is that if I do anything that causes the connectionstring to change in the global.asa file, I must re-insert the slash. The problem according to MS appears to be something with the server administrator not keeping things synchronized, but it looks like the problem could be checked for in the rest of the global.asa file.



dshayden -> RE: DRW Error - 2003 (10/18/2004 22:07:20)

I am still having trouble adding an "edit" function on records already in a database (new records post to the database fine) in FP2002/Access2003 (dshayden, posts in another thread).

I successfully did this change to friendly error messages, and I get:
Database Results Wizard Error

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.

See Microsoft Knowledge Base Article 817029

But the Microsoft solution is to switch to Asp.net, and I don't know if my server even supports asp.net or have it locally.

Sorry to be such a newbie. Is your solution of switching out old include files a solution for this message? I'm a little unclear from reading other posts. Could you explalin how to switch them out exactly? I already downloaded them.

Thank you very much.




Spooky -> RE: DRW Error - 2003 (10/18/2004 22:19:17)

I would give them a try - keep backups of the original includes (althought they are easily replaced)



dshayden -> RE: DRW Error - 2003 (10/18/2004 22:28:09)

Ok, I am actually making progress, but the update is not really happening. I ftp's the old 2000 fpclass files up to my webserver, and now I don't get the error message anymore! In fact, the message says, "update successful," (since that's the message I put in the "no records returned" field).

So the process is working ..... except..... the record is not actually updated. I am gong to close out to clear out the cache and try again.



ChrisOne -> RE: DRW Error - 2003 (1/21/2005 9:09:51)

This problem happened to me and i don't even use FP2003. Windows Automaic Update actually updated the .inc files in the _fpclass folder in my web - WITHOUIT ME EVEN KNOWING ABOUT IT - and susequently caused all my DIW pages in my FP2002 web to fail.

Took me a while to work that one out!!!

Then used your "easy fix".

Perfect. You are a genius!

Thanks



BobGeezer -> RE: DRW Error - 2003 (3/12/2005 13:22:03)

Has this problem ever been fixed by Microsoft? I'm limping along with FP2000 because I'm afraid to ruin all my sites by using it.



evansforsyth -> RE: DRW Error - 2003 (3/12/2005 19:00:42)

Haven't had the problem since installing FP 2003 into a separate directory. I still suspect that if FP is installed as an update, then FP messes up in this area.

If I'm correct, then people installing FP2003--who have not had FP before--should not have this problem. They will be wondering what we are talking about!

Again, if I'm correct. Install the new FP into a totally different directory--don't upgrade. OK, so if you bought an upgrade can you install that into a new directory . . . I don't know, just have to try it.

Anybody else tried this?

Evans



BeTheBall -> RE: DRW Error - 2003 (3/19/2005 19:44:09)

quote:

ORIGINAL: Joey

I went back to FP2000 & this is the error I get.

Database Results Error
Description: Data type mismatch in criteria expression.
Number: -2147217913 (0x80040E07)
Source: Microsoft JET Database Engine

I know I was able to update a database a few years ago but I cannot remember how, Any suggestions?


Post the above in a new thread and include the SQL statement you are using.



tomsrig -> RE: DRW Error - 2003 (5/3/2005 15:36:15)

Hi, all,

I'm new here and new to Frontpage 2003.  HELP [image]http://www.frontpagewebmaster.com/micons/m14.gif[/image]

My question is on the same subject in this thread. 

Namely that I get a - The operation failed.  Please contact your server administrator - message when I try to click on the SUBMIT or ACCEPT change buttons in the ASP.NET data base I am trying to create.  This is driving me nuts!!!  I have managed to create a ASP type database and it works OK.  But it does not have the functionality I want that exists in ASP.NET. 

I have created a INTRANET website for my engineering office.  I own the server and am the administrator of it.  The server is running Windows Server 2003, and IIS 6.0 is installed and running, and ASP.NET is allowed.  In fact, I've allowed most everything - since I'm the head guru. 

I created my website at the root level.  There is only one website currently on the server until I can find out what is going on with this database problem.

I have Frontpage 2003 running on my desktop computer.  Next to it is the above webserver linked via our network.  All works great in that fashion.

So, I do all my work in FP 2003 and all seems to work with it until I try to create a ASP.NET database.  However I create the ASP.NET database, it makes no difference the failure.  When pressing the Submit or Accept changes button that got created when I use the Database Wizard and place the database in the CURRENT website, and validate the database link and all that - It still won't work.  All the other form buttons work.  By the way, I created my database having the following forms; SUBMIT, EDIT, RESULTS.  In the SUBMIT form structure there is that SUBMIT and RESET BUTTON.  In the EDIT form there is the RESULTS FORM and the EDit section where you have ACCEPT changes, CANCEL changes, RESET this record, Delete this record buttons.

Only the ACCEPT changes or the SUBMIT buttons do not work.  Obviously it can not link up and update the database. 

To test this out in very simple fashion.  I created only one text box along with the above buttons.  In other words, I let the Database wizard do all the work - no modifications or anything - I just let the Wizard do its thing.  Well, something is not right with Microsoft.  My server works fine with everything else, and my website works fine, and my ASP database (used to test this function) works fine.  ONLY ASP.NET database SUBMIT or ACCEPT won't work.

I guess I'm repeating myself, cause I'm frustrated.

Any help from you folks would be appreciated.  I have read the other posts here, and will go over them again and try a few things.  But I just wanted others to know that right out of the BOX this FrontPage 2003 has this problem and if it has a problem due to Windows Server 2003 and ASP.NET funtion - Which is also brand new - I can't tell that.  Only that the ASP.NET database function will not work at all.

Best Regards,
Tom






Spooky -> RE: DRW Error - 2003 (6/8/2005 17:20:40)

Please - if you have a problem, start a new thread.

If you have any positive input into this thread, then by all means add it here.
Otherwise START A NEW THREAD WITH YOUR PROBLEM



sgano -> RE: DRW Error - 2003 (6/8/2005 20:53:48)

Tom, I had a similar problem in that I could add records, delete records, but I couldn't update. It turned out that I had used a reserved word as one of my field names in my database. I tried using Microsoft's fix, but it didn't work, so I had to go back and rename the field and rebuild the results and editor pages....argh. At any rate, it's working now (thank goodness). I believe the offending field name that I had originally used was the word "date". Hope that helps. I was nearly in tears before I finally figured out what the problem was [sm=rolleyes.gif]



polyclay -> RE: DRW Error - 2003 (7/14/2005 13:56:30)

Thank Heavens I found this page!!

I SERIOUSLY thought I was going to have to give up the business altogether. In fact I'd already started the process to move to another platform so I won't be so dependent on FP features. Maybe I can reconsider now!

It worked for me to replace the FP includes with the old ones. It did not work just to edit the code--for some reason that worked for plain Selects, but not for any other SQL like Insert or Update. It had also not worked simply to delete FP2003 and republish with 2002. As other people have found, my problem came when I installed the Office update.

This forum is a LIFESAVER! Thanks!!



DAK -> RE: DRW Error - 2003 (7/20/2005 21:07:37)

I echo Poly's sentiments..... I can't have too many lives left!

My problem was as Sgano suggested. You can't use 'Date' as a database field name. Once I recreated, using something like "StupidDateField", it worked!




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.21875