Database Results Wizard Error

[Makafee]

I used the Database Interface Wizard to build a site for testing purposes.
After publishing the site, it allows me to enter new records into the Access
database, but not to update those records from the edit page.

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

Any idea what's going wrong? If I contact my server administrator, what
questions do I ask?

TIA

 

[Kathleen Anderson [MVP - FrontPage]]

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


--

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

 

[Makafee]

Thanks, Kathleen, that helped. Initial error was actually reporting fields
left blank, please provide default values, blah, blah.
Having no notion if the fp_sQry line supports an 'immediate if' type
operation or what the syntax would look like, and not understanding exactly
what the fp_sDefault line is meant to accomplish, I set up default values for
all fields in the database itself. Seemed to work, that is I created a new
record in the database and when I opened it for editing, none of the fields
were blank.
Now when I change values in the 2 fields required and attempt to update the
record I get a new error: "Syntax error in UPDATE statement". *sigh*

FYI, I'm using FP2003 SP2 on Windows Server 2003, with support for FP
Extensions and ASP. I am trying to set up a Service Request database. A
user creates the service request record by providing entries forthe first 10
fields of the table. There are 4 more fields in the table that do not appear
on the submission_form. Those are for support personnel to update, to keep
track of the progress of the request. Sounds simple, eh?

Your help is greatly appreciated.

 

[Makafee]

Fanfare of trumpets! Thanks to half-a-dozen posts from various people over
the last 2 years, I found an answer...in the 'Duh' category. I had fields
named "DATE", "NAME", and "ERROR". Now that those fieldnames have been
changed, I can update edited records.

Thank you all.