Re: Row cannot be located for updating error - persistent but inconsistent

Clay Fox — Thu, 10 Apr 2008 16:40:03 GMT

Hi Dawn.

Sorry to hear of these issues. I have seen similar issues before in multi-user environments with Access.

Unfortunately I believe this is an Access issue. Access is really not designed for this kind of utilization. Its performance as well as network and client performance could all contribute to these inconsistent types of errors. With the default DB connectivity, InfoPath is always checking the form state vs what is in the tables and what is in the form and this is breaking down and causing this error, it could also be due to multiple people trying to update related records.

SQL, even SQL Express, is the appropriate component for an enterprise InfoPath solution. Being tuned and designed for this activity.

Also web services would be the preferred communication mechanism as they require less bandwidth, are more forgiving, and much of the processing can be off-loaded to the server.

I would guess you would likely experience some of these issues even using an Access form since it is outstripping is base competencies.

Send me an email if you would like to discuss further or if I can help in any way.

Row cannot be located for updating error - persistent but inconsistent

hugs4thetrees — Thu, 10 Apr 2008 15:46:57 GMT

I have been plagued with this error for several months now and we are about to scrap 6 months worth of work in InfoPath if I cannot resolve the issue. I was able to submit my form on my computer 35 times yesterday with no problem. Another user tried today and got the error after 9 submit.

I am using Infopath 2003 connected to an Access Database. I have no fancy code behind the scenes that would be causing the error but I do think it might have to do with how the recordset is being updated.

The form works like this. Dataconnection is tblMainInfo linked to tblTerm (linked by AuditNumber which is an autonumber generated field)

User enters basic data (name, date, etc...) and hits a submit button. The data is sent to Access database and primary key is set in the Access table. User can then view the next section of the form that is based on tblTerm. This is a repeating section with a submit button on it. User should be able to enter and repeat this section as many times as they'd like but here is were the Form could not be submitted. Row cannot be located for updating.... error. Sometimes after 2 submits sometimes not at all even after 35 submits!! ???

EVERYTHING I have read points to primary keys or SQL coding that has nothing to do with my simple form. I have primary keys on both tables. I still get the error even when just using one table so it's not the connection between the two. In my Access table, the primary key defaults to Long Integer type and cannot be changed but I changed all other non text fields to Double. Text fields still say Simple though. I have removed all default values from the Access table. I have read posts that say doing these things will fix the problem but it has not.

I recently read something about using a SET NOCOUNT ON statement but don't know the first thing about using the script editor and what this statement would include. It's not nearly as helpful as Access's script editor....

Has ANYONE ever gotten this error before and resolved it? Like I said 6 months of work goes down the drain tomorrow if I can't resolve the issue. I'll have to resort to using Access only and it is so SLOW on a shared network that I really do not what to do this. PLUS I really need the "repeating section" functionality of Infopath!

Hoping and praying for a final solution!

Thank you - Dawn

Newbie Questions

Re: Row cannot be located for updating error - persistent but inconsistent

Row cannot be located for updating error - persistent but inconsistent