Well, that seemed to solve the problems I had with formsview, but I cannot get this to work with gridview.

I have now hardcoded the update statement and still get the error !

Does anyone have any idea what's wrong  (works fine in Toad) ?

This is driving me nuts.

thx

<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConflictDetection="OverwriteChanges"

ConnectionString="<%$ ConnectionStrings:Tempus %>"

DeleteCommand='DELETE FROM T_TIMESHEET WHERE TIMESHEET_ID = :original_TIMESHEET_ID'

OldValuesParameterFormatString="original_{0}"

SelectCommand='SELECT * FROM T_TIMESHEET WHERE (ENTRY_DATE >= :ENTRY_DATE and ENTRY_DATE < :ENTRY_DATE + 7) ORDER BY ENTRY_DATE,CREATION_TIMESTAMP'

UpdateCommand="UPDATE T_TIMESHEET SET TASK_ID = 1 WHERE TIMESHEET_ID = 28"

ProviderName="<%$ ConnectionStrings:Tempus.ProviderName %>"

InsertCommand='INSERT INTO T_TIMESHEET (TIMESHEET_ID, USER_ID, ENTRY_DATE, TASK_ID, REFERENCE_ITEM, DURATION, COMMENTS, CREATION_TIMESTAMP, UPDATE_TIMESTAMP, REPORTED) VALUES (seq_t_timesheet.nextval, :USER_ID, :ENTRY_DATE, :TASK_ID, :REFERENCE_ITEM, :DURATION, :COMMENTS, sysdate, sysdate, :REPORTED)'>

<DeleteParameters>

<asp:Parameter Name="original_TIMESHEET_ID"/>

</DeleteParameters>

<UpdateParameters>

</UpdateParameters>

<SelectParameters>

<asp:ControlParameter ControlID="Calendar1" Name="ENTRY_DATE" PropertyName="SelectedDate"

Type="DateTime" />

</SelectParameters>

<InsertParameters>

<asp:ProfileParameter Name="userID" PropertyName="userID" Type="Decimal" />

<asp:Parameter Name="ENTRY_DATE" Type="DateTime" />

<asp:Parameter Name="TASK_ID" Type="Decimal" />

<asp:Parameter Name="REFERENCE_ITEM" Type="String" />

<asp:Parameter Name="DURATION" Type="Decimal" />

<asp:Parameter Name="COMMENTS" Type="String" />

<asp:Parameter Name="REPORTED" Type="String" />

</InsertParameters>

</asp:SqlDataSource>

----------------------------------
Timestamp: 08:42:19.149
UPDATE T_TIMESHEET SET  TASK_ID = 1 WHERE TIMESHEET_ID = 28
Execution time: 0 ms
Runtime error occurred: 1036 (ORA-01036: illegal variable name/number)

OK - thought of a way round this, but I need a little help.

 

What I'm doing is catching the rowupdating event, updating the database in code behind, which I know works, then cancelling the update using e.cancel.

This is fine, but leaves the row in edit mode (showing the update/cancel links), rather than putting the row back in display mode and refreshing the grid.

Can someone tell me how to do that ( get the row back into display and refresh the grid)?

 

thx very much

Graham 

That doesn't work, because you can't force a page refresh from the server.

This is really proving to be a showstopper.

Doesn't anyone from MS ever read these posts ?

OK, went back to basics and recreated the page from scratch (not using copy & paste from the old one) and..... it worked.

There must have been some corruption of the old page somewhere.

So, I formatted the grid a bit to make it look better; hid some fields etc. and got on with some testing.

I then found that certain fields were being wiped out during an update.

It turns out that it was the invisible fields !!! If a field is not visible, gridview doesn't update it; actually no. If that were the case, it would be OK, but it actually nulls the field out!.

I tried removing the fields from the update statement and update parameter list and guess what - I got the ORA-1036 error again. Yet everything matched up.

I then tried to refer to the field with the original_ prefix, after making sure it was defined (

OldValuesParameterFormatString="original_{0}" )  and again got the ORA-1036 error.

Is this flaky or what ?

Of course, it's not likely to get fixed as I can't see anyway of feeding this back to MS except via these forums and it's quite apparent that no-one from MS ever comes here.

Really makes you glad you did the right thing and paid for it, doesn't it?

 

Just in case anyone else has this problem, it turns out that OldValuesParameterFormatString="original_{0}"  was the problem.

Removing it allowed me to remove the fields that the gridview was blanking out and enable updating to work ok.

For some reason I couldn't remove one field that wasn't being updated. It has a valid value in it, so it's not a problem. But I just can't see why I could remove some fields, but not others.

Also, how on Earth can I refer to old values when defining the OldValuesParameterFormatString stops the gridview working ?

Hi

Atlast found how to set Conflict parameter - but even after setting to Overwritechanges and setting

OldValuesParameterFormatString="original_{0}"

 The exception doesn't go away - it still says ORA-01036:illegal variable name/number.

Please let me know how to overcome this problem.

Sri

I searched and searched for a suitable methed to cancel the edit. The only solution I managed to come up with was refresh the page with a Server.Transfer("page.aspx"). If there were any page/control settings which were set in the page I put them into session variables which I checked in the page load.

Not the preferred method, but it is working for me. If there is a better method; I am all ears!

Sri,

try removing the OldValuesParameterFormatString setting

Graham

Tried - didn;t help

Post your aspx file and I'll see if I can help.

You using Oracle ?

Sending the ASPX file TimeCard '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> '> " ProviderName="" ConflictDetection="OverwriteChanges" SelectCommand="SELECT rtrim(timv_paycode) || rtrim(timv_order_nbr) || rtrim(timv_control_id) as timv_paycode ,timv_operation_id,timv_sat_time,timv_sun_time,timv_mon_time,timv_tue_time,timv_wed_time,timv_thu_time,timv_fri_time,timv_post_department,timv_post_division FROM "TIMV" WHERE ("TIMV_EMPLOYEE_NUMBER" = '23909') and timv_week_ending_date = '03-MAR-06'" UpdateCommand="UPDATE timv SET timv_sat_time=4 WHERE ("TIMV_PAYCODE" = '115' and "TIMV_EMPLOYEE_NUMBER" = '23909') and timv_week_ending_date = '03-MAR-06'" DeleteCommand="delete from timv where timv_employee_number='23909' and timv_week_ending_date='03-MAR-06' and timv_paycode='115'" > /form>