InfoPath Dev

Hi,

I have found that a submit action to a main data connection from a secondary view doesn't work.  I guess I am learning here about views and what there limitations are.  Can someone confirm that this is the case? Submit actions to the main data connection only work on 1 view. 

If this isn't the case, can someone explain to me why when I remove the submit to the main data connection in my second view the buttons work? The button only has now submit actions via Email and doesn't include any connections to the main data connections (SQL). The emails work great.

The error that I was receiving was

InfoPath cannot submit the form.
An error occurred while the form was being submitted.
[0x80040E38][Microsoft Cursor Engine] Row cannot be located for updating. Some values may have been changed since it was last read.

My intentions of the second view was to organize the main view a bit, but I might have to put it back into the main view so that the submit actions work with the connections to the main data connection.

Are there any workarounds to include a second view and have the submit actions work to the main data connection?

Thanks everyone.

Actually, I haven't run into this before. I've build database bound forms with multiple views and have not had an error on submit. You aren't trying to modify the  primary key in any of your rules are you? Could some other app change the data in the DB between the time you opened the form and the time where you tried to submit?

Hilary,

Perhaps you will understand better if I explain the workflow.  The workflow is for a help desk ticketing process.

1st Submit

Requester fills in requirements

Clicks "Submit" which does the following via rules:

Connects to Main Data Connection in SQL (Creates a ticket ID)

Form is then emailed as an attachement to help desk.

The form closes.

2nd Submit

Help desk then opens the form from email.

Clicks a different submit button labeled "Assign" which does the following via rules.

Connects to Main Data Connection in SQL (SHOULD UPDATE THE RECORD IN SQL)

The form is then emailed to another group of people as an attachment.

The form closes.

The above process did work for a while without the below error

InfoPath cannot submit the form.
An error occurred while the form was being submitted.
[0x80040E38][Microsoft Cursor Engine] Row cannot be located for updating. Some values may have been changed since it was last read.

but after some changes to the form it now won't let the record be updated.  These changes, to my knowledge, are normal design changes that relate to look and feel of the form. I don't beleive that any changes that may have invited this error was done.  Well, at least I don't think so anyway. 

Question: Why would a form with this setup work one day and not the next?

I did research and read an article in this forum about creating a query button and having the user click that query button before makeing updates and submitting.  This works but is totally not going to be something I want to have users do all the time. 

What advice can you provide me after reading this response?

Thank you Hilary.

Here are answers to your two questions:

You aren't trying to modify the primary key in any of your rules are you? 

I don't want to modify the key itself but the fields in that table for that corresponding primary key.

Could some other app change the data in the DB between the time you opened the form and the time where you tried to submit?

Yes, changes are occuring on records in the table, but on records that are already in the table (users update the table via another form, but for already existing records only).  The issue arises from new records being created during the 1st submit I described previously.

I hope that I answered these for you.

I was wasn't able to pin point exactly the cause, but was able to isolate the section that was creating the problem.  As a result, I re-created that section and it isn't an issue now.  Thank you.