ASP update error

[Cliff Hooker]

Now I know this code works on IIS5.0, trying it on a Windows2003 server (IIS6) I get this lovely error which I can not trace, I think it's something either on IIS6 or the server but any suggestions welcome....

On loading the update page I get the error...

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

The SQL code is UPDATE t_deeds_main SET deed_no='::deed_no::' WHERE id=::id::

As I say, works fine on IIS5, and I can view asp pages OK on IIS6 but adding a custom query just throws it.

Any help appreciated.

Setup:- FP2003, IIS6, SQL2000SP2 (SQL and IIS on separate boxes).

 

[Cliff Hooker]

Found the rather odd answer...

On the page that performs the update FP2003 fails to put in the s-columnnames and s-columtype values in the <!--webbot.. region!!!!!!!

You have to manually put these in!!!!!!

Sounds like a bug to me. Here's the very useful note I found on the issue...

http://www.frontpagetalk.com/forums...ace_Wizard/m_50766/p_1/tmode_1/smode_1/tm.htm

Now I know this code works on IIS5.0, trying it on a Windows2003 server (IIS6) I get this lovely error which I can not trace, I think it's something either on IIS6 or the server but any suggestions welcome....

On loading the update page I get the error...

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

The SQL code is UPDATE t_deeds_main SET deed_no='::deed_no::' WHERE id=::id::

As I say, works fine on IIS5, and I can view asp pages OK on IIS6 but adding a custom query just throws it.

Any help appreciated.

Setup:- FP2003, IIS6, SQL2000SP2 (SQL and IIS on separate boxes).

 

[Hari]

Hi Cliff,

Please turn on the ASP.net debug messages flag. You can do that by using
the following steps.

Turn on the "Show Hidden files and folders option under Tools-> Site
settings->Advanced tab.
Open the files fpdbnet.cs in the _fpclass folder
Search for the line Private bool Debugon = False;
replace it with private bool DebugOn = true;

When you do the above steps, the error message will change to the following.

Debug message : Dynamic SQL generation for the UpdateCommand is not
supported against a SelectCommand that does not return any key column
information.

If you are getting the same behaviour as explained above, then the reason
for your error might be related to the absence of primary field in the
table.


Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights