InfoPath Dev

I am submitting a form to an Access database which uses an  AUTONUMBER field for a key. I can save the form initially but when i re-open the form and make a change and then select submit again I get the following error.  Do you know what I do to fix this? 

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.

I added a condition on the submit to check for the key and it works now

OK, to help people who do not yet know what causes this failure I have found that it is due to 2 competing "datasets".  One is the one held by the form and the other is the one held by the database.  From what I can work out InfoPath knows what data you have changed but when checking it with the database finds an anomaly in either 1) the rest of the data or 2) the primary key does not match.

IMHO I believe it is 1)

Used to get it where someone has a form open or saved on their local computer and someone else modifies the database or more specifically their line in the data.

I am also guessing that if the database is not on record-level locking in access that could cause it if the database table is open, if record level locking then is used it must be down to the record being used.

I hope this helps

Adam

Can you explain how you added the condition? I have the same problem with a form.

 Thanks.

Heath

I'm having this same problem with a form.  I have the form submitting to the Main connection first and then to the SharePoint library.  The form submits fine but it gives the error message when I resubmit the form.  I was trying to get the SharePoint document name to be the date submitted and the primary id field in the main database table.  I have discovered that on earlier versions where the data submitted to the SharePoint library without the primary key, it will resubmit ok the 1st time.  It gives the error if you try to pull up the same document and resubmit again (it now has the id field populated).  So what kind of rule and where and when would I activate the rule in order to get the ID field in the document when it was first submitted to Sharepoint and then be able to resubmit with corrections without this error.

Thanks

I actually ended up adding an id field to the form and a query button that queries the fields that were changing. The button only appears after certain fields (status, assigned to) have new values. I included a note on the form for the user to hit the query button, then change anything they need to after the query, and then hit the submit button. Works like a charm.

I think I have narrowed down the problem.  The form had a rule on a section and it was causing problems once it was submitted,so I removed the rule and found another way to accomplish the same thing.  I've removed several sections and tables and adding them back one at a time.  It seems to be working ok.  I havent' been working with InfoPath very long and we just installed SharePoint so I know very little about it.   I would like to use the form to query up all the records in the database that haven't been verified, in the same format as they were when they were submitted and the auditors could go thru them down the page, make any corrections and submit the bunch in one submit.  Is this possible?  The plan for now is they are going to Sharepoint in individual documents and each one will be opened, edited and submitted back to the database.  It just seems like there would be a better way but I don't know how to write code.

Do anyone have any suggestions for me?

Thanks

Sandy