Frustration with Database Interface Wizard

Frustration with Database Interface Wizard (Full Version)

FrontPage Talk - Great Talk About Microsoft FrontP: http://www.frontpagetalk.com/forums/
- Taking FrontPage Further: http://www.frontpagetalk.com/forums/default.asp?catApp=3
- - FrontPage and Databases: http://www.frontpagetalk.com/forums/appid_3/tt.htm

Message

Geo -> Frustration with Database Interface Wizard (11/23/2003 4:18:51 PM)
I am currently using FP2003. I also am very diversified in databases development which makes this even more frustrating. I am having a constant problem using the Database Interface Wizard, "DIW" when it comes to the Editing part. After the DIW is successfully created it allows me to ADD New Records DELETE Existing Records but when I try to EDIT a record it always does this. First I > Select a Records > click to Edit the Record (add some editing) then each time after EDITING a record and I click >OK I get > "Database Results Wizard Error - The operation failed. If this continues, please contact your server administrator." I must have the folder permission set correctly otherwise I wouldn't be able to ADD and DELETE as I do. INTERESTING NOTES: 1. If I use the sample Northwind DB while setting up the DIW it works! BUT: 2. If I create a database during the DIW it freezes during the editing ONLY. 3. If I create an Access DB and import it into the website it freezes during the editing ONLY. I even went so far as to publish the Northwind DB (because it worked) to my local machine then opened it with Access 2002, made some field changes and renamed the DB, imported it back into my FP website into ../fpdb, set the folder permissions then tried it............it frooze during the click of the OK button during the EDITING process giving me the same error message as before > "Database Results Wizard Error - The operation failed. If this continues, please contact your server administrator." The amount of time I have spent on this simple project is overwhemling. Is there something I am overlooking or is there a 3rd pary program that works better than the FP DIW or is there a better way??? I will really owe you one if you can solve this one for me. Geo

TexasWebDevelopers -> RE: Frustration with Database Interface Wizard (11/24/2003 6:50:48 AM)
You've given us a taste of the problem but not enough information to find a solution. Are you hosted on a Unix server or a microsoft server? Is the database in the fpdb folder or did you rename the folder to something else? Have you checked your field names for "illegal" sql names in the fields?

Geo -> RE: Frustration with Database Interface Wizard (11/25/2003 8:04:36 PM)
The site is hosted on a Window Server. The database directory is /fpdb. I did another test to see what may be causing a problem that I am have ONLY with the Editing part of the Database Interface Wizard. I once again used created a DB using the DIW using the northwind sample and ALL functions worked as before. The DB File was placed in /fpdb and the DATABASE connection was Verified. Then I again used the DIW to create a DB but this time I used the option; Create a new Microsoft Database within your website. Created a few fields and went through the same procedure as the northwind including placing the DB in /fpdb and the DATABASE connection was Verified. The the permissions were set; Allow scripts to be run, Files to be browsed. ------------------- Opening IE6 I went back to FP2003 and copied the file (path) of the Database Editor from the northwind in the address bar of IE6. And did all the following successfully: 1. Added a New Record 2. Deleted a Record 3. And Edited an Existing Record I then went back to FP2003 and copied the file of the Database Editor from the New DB that I created from a few fields. I was able to: 1. Added a New Record 2. Deleted a Record 3. But when I tried to Edited an Existing Record it once again gave me the error, "Database Results Wizard Error The operation failed. If this continues, please contact your server administrator." --------------- Figuring that the only file responsible for this action was the "update.asp" which was created during the creation of the DIW I opened the both the update.asp in the northwind file structure and the update.asp in the new DB file I created with a few fields. Comparing the code in FP2003 side by side I saw that there was absolutely NO difference with exception to the field names, table name and fp_sDataConn . Still very confused as to where to even start to try and find the problem. George

TexasWebDevelopers -> RE: Frustration with Database Interface Wizard (11/25/2003 11:38:50 PM)
what are your field names?

elliotm -> RE: Frustration with Database Interface Wizard (12/5/2003 2:48:06 PM)
[:@]I am unfortunately having the exact same problem when I use the wizard in FP 2003 and add a custum query with an UPDATE. I have the same setup working properly on a site that was created in FP 2002. All other SQL statements have been working properly in the wizard except UPDATE. I believe it has something to do with FP 2003, but what, I am not sure. FP 2003 uses the same extensions as 2002. I have also been pulling out my hair over this problem. If I make any progress I will be sure to post it.

Bud -> RE: Frustration with Database Interface Wizard (12/9/2003 5:48:55 AM)
Make sure that you have present all fields, in the table, in the form, whether visible or not. Or.... When you create a table with FrontPage.... Look at the fields created. Check the list of saved fields.

swelch -> RE: Frustration with Database Interface Wizard (1/5/2004 11:18:40 AM)
I'm having the same problem. I think this is a problem with fp2003 DRW but microsoft does not have any articles on the error. If you edit the fp_DEBUG = True line in fpdbrgn1.inc and change the value from FALSE to TRUE, you will get the following error when you try and update: 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. You may need to read Microsoft Knowledge Base Article 817029. The article does not exist and I have tried to add the missing columns and types to no avail. I'm at a loss. Any help would be greatly appreciated.

alienzhavelanded -> RE: Frustration with Database Interface Wizard (1/10/2004 3:02:38 PM)
It seems that FP 2003 changes things slightly in the way it codes certain things compared to 2002. Happy coding The Martian

kidro2 -> RE: Frustration with Database Interface Wizard (1/25/2004 8:39:17 AM)
I'm also having the same problem with FP2003. The only articles I have read on this mentioned the use of the field name "Timestamp" which is an SQL command and not valid to use in queries without surrounding it in brackets (i.e., [Timestamp]) to identify it as a field. Unfortunately, this is not a solution for me....I don't have this field in my DB. When you let Frontpage generate the database for you, it puts it in by default. I even tried that and used MS's suggestion, but no go. I have tried this so many different ways, but I have to be missing something. I'm gonna keep pounding away at this, but if anyone finds any info at all, please pass it along to us poor souls.

kidro2 -> RE: Frustration with Database Interface Wizard (1/25/2004 11:08:27 AM)
Ok folks, I may have found a solution. The key is in the message: "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. You may need to read Microsoft Knowledge Base Article 817029." ...which is displayed after setting fp_DEBUG to True in the fpdbrgn1.inc file as mentioned previously. (Of course, that KBA 817029 is non-existent.) 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" Regardless, this worked right way for me and I'm a happy camper after spending hours troubleshooting.

Easily_Befuddled -> RE: Frustration with Database Interface Wizard (2/16/2005 8:09:22 AM)
I just want to thank everyone who posted in this thread. I stumbled on here via google after having the same problem, and using what I learned here I was able to solve it. Who knew that FrontPage 2003 could be such a pain? Thanks again to everyone! (Especially Kidro2 and swelch)

canuck21a -> RE: Frustration with Database Interface Wizard - Some Success (3/24/2005 10:26:27 AM)
Please note that I have had a small degree of success with oneof my more simple database tests with FP2003. I too was..maybe still am..frustrated with things that simply do not always work. Front Page 2003 DataBase Editor Wizard - Problem with Edit not being accepted. 1. Read the article from the forum on the missing parts of the webbot, but my update.asp page had the correct values.....still did not work. 2. Had previoulsy read somewhere about a Microsoft bulletin about failed FP wizard database updates. 3. The article indicated the the update fileds need to be in brackets, like [NAME] as opposed to simply NAME. (My version: SET Date versus SET [Date}) 4. I decided the try that in the Update Query (see second section of my file details) FP would not let me change it for some reason so I edited it in a trext editor and saved the file. 5. Tried the database editor on a record and it was now accepting changes. <!--webbot bot="DatabaseRegionStart" s-columnnames="ID,Date,Details,Author" s-columntypes="202,202,202,202" s-dataconnection="notices" b-tableformat="FALSE" b-menuformat="FALSE" s-menuchoice s-menuvalue b-tableborder="TRUE" b-tableexpand="TRUE" b-tableheader="TRUE" b-listlabels="FALSE" b-listseparator="FALSE" i-ListFormat="0" b-makeform="FALSE" s-RecordSource s-displaycolumns s-criteria s-order s-sql="UPDATE Notice SET Date = '::Date::' , Details = '::Details::' , Author = '::Author::' WHERE (ID = ::ID::)" b-procedure="FALSE" clientside SuggestedExt="asp" s-DefaultFields="Date=&Details=&Author=&ID=" s-NoRecordsFound="Record updated in table." i-MaxRecords="1" i-GroupSize="0" u-dblib="../../../_fpclass/fpdblib.inc" u-dbrgn1="../../../_fpclass/fpdbrgn1.inc" u-dbrgn2="../../../_fpclass/fpdbrgn2.inc" Tag="BODY" startspan BOTID="0" preview="<table border=0 width="100%"><tr><td bgcolor="#FFFF00">< font color="#000000">This is the start of a Database Results region.</font></td>< /tr></table>" --><!--#include file="../../../_fpclass/fpdblib.inc"--> fp_sQry="UPDATE Notice SET [Date] = '::Date::' , [Details] = '::Details::' , [Author] = '::Author::' WHERE ([ID] = ::ID::)"

Bud -> RE: Frustration with Database Interface Wizard (3/24/2005 12:57:09 PM)
The easiest fix is to find someone who has a copy of FrontPage 2002 Ask them for a copies of the following files. fpdbrgn1.inc fpdbrgn2.inc fpdblib.inc fpdbform.inc Replace your copies with the copies created with FP 2002 You will see that the file (fpdbrgn1.inc) created by FrontPage 2003 is 16.61kb where the file (fpdbrgn1.inc) created by FrontPage 2002 is only 8.02kb, Update and Delete when using the file (fpdbrgn1.inc) created by FrontPage 2003, what I've seen contain a bug that has not been fixed nor does it seem to be getting any attention from Microsoft. However, Microsoft does admit that you should upgrade the ODBC drivers on the server, which they then inform you of an incompatability with Update and Delete. THere suggestion is to attempt the use of .Net

David_Dunster -> RE: Frustration with Database Interface Wizard (3/25/2005 11:42:34 AM)
This may help but I have never used the DIW, just had problems similar to yours with DRW. I have read that ASP does not enjoy working with "../../../_fpclass/fpdblib.inc" where ASP.NET has no problem. It appears that it can't handle the "../" scenario. I have the same problems. What I did was make an "_fpclass" directory in the same directory as the asp pages and placed copies of all .inc files in the directory. In my situation, I did a search for "../_fpclass" and changed all occurences to "_fpclass". In your case, you would want all of the "../../../_fpclass" to be "_fpclass" That may work for you. I also used the 2002 .inc files instead of the 2003 .inc files. I have serveral databases that now work properly. You can see them at www.cdnhams.ca under the "IC Database" option. Hopefully this will help you.

Bud -> RE: Frustration with Database Interface Wizard (3/25/2005 9:22:27 PM)
In order for ../../folderName to work... The hosting server needs to support Parent Paths If the option is not enabled in Windows based servers... Well need I say more. This problem can be fixed by simply asking your provider to enable Parent Paths.

chillwa -> RE: Frustration with Database Interface Wizard (2/19/2008 10:07:42 PM)
I had the same problem and found a fix. I had to actually adjust the table field settings in MS Access in order for the update query to work. (my add and delete queries worked fine) I opened MS Access, opened up the table in design view. Looked at each field and changed the featured that said "Allow zero length field" to yes and the "Required" field to NO (under the General tab) for all of the table fields that had this option. I deleted an OLE field on one table, because it did not have this option. Everthing worked fine after that. So it's worth a try. I no longer get the database wizard error in .asp when using the update/edit query in the database editor created with the frontpage database interface wizard.

Page: [1]