Row cannot be located for updating - InfoPath Dev
in

InfoPath Dev

Row cannot be located for updating

Last post 12-18-2007 09:30 AM by Tom Jenkins. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • 09-01-2006 11:25 AM

    • Deborah
    • Not Ranked
    • Joined on 09-01-2006
    • Trinidad and Tobago
    • Posts 8

    Row cannot be located for updating

    Goodday,
    I am getting this error on a submit button. I changed the length of a field on a Sql Server 2000 database. Now old forms cannot submit to the database. I am submitting to the database using a rule and the submit wizard.

    Any suggestions are greatly appreciated.

    Regards,
    Deborah
  • 09-02-2006 12:06 AM In reply to

    Re: Row cannot be located for updating

    Hi Deborah and welcome to our forum from Trinidad and Tobago!
    Do new forms work? Unfortunately, schema changes do cause form incompatibilities. We have developed a database accelerator Web service that removes the tight coupling and lets you change the schema on either side without any problems. However, you likely just want to get yours working with minimal hassle and change. You'll want to implement some update code to update old forms so that they are compatible with your new SQL schema. This will requre some work. First step is understanding what changed exactly. Can you tell us how you changed the field length?
    =
    Patrick Halstead
    Project Manager at Qdabra
  • 09-04-2006 10:41 AM In reply to

    • Deborah
    • Not Ranked
    • Joined on 09-01-2006
    • Trinidad and Tobago
    • Posts 8

    Re: Row cannot be located for updating

    Thanks for the warm welcome to your forum. I greatly appreciate your assistance.

    I changed the field by expanding the width of the field in the design view in Enterprise Manager.

    Thanks,
    Deborah
  • 09-04-2006 01:31 PM In reply to

    Re: Row cannot be located for updating

    Hi again,
    Thanks for the clarification. What is the error you receive when submitting old forms? If you change the field back to the previous width, do the old forms work again?
    Patrick Halstead
    Project Manager at Qdabra
  • 09-06-2006 08:40 AM In reply to

    • Deborah
    • Not Ranked
    • Joined on 09-01-2006
    • Trinidad and Tobago
    • Posts 8

    Re: Row cannot be located for updating

    Hi Patrick,
    The following is the error obtained:
    [0x80040E38][Microsoft Cursor Engine]Row cannot be located for updating. Some values may have been changed since it was last read.

    In attempting to change the field width from 1000 back to 300, I get a warning that some of the data may be lost....really do not want to lose data.

    Regards,
  • 09-11-2006 11:03 PM In reply to

    Re: Row cannot be located for updating

    Hi again,
    Sorry for not responding sooner. I'm going to ask our DB experts to look at this thread. Lately, we have had some of the same problems, so hopefully it will be an easy resolution. More soon!
    Patrick Halstead
    Project Manager at Qdabra
  • 11-29-2007 11:15 AM In reply to

    Re: Row cannot be located for updating

    Any more info on this yet?

  • 12-18-2007 09:30 AM In reply to

    Re: Row cannot be located for updating

     

    Hi, we get a similar problem.  We have created forms with a SQL Main Data Connection but also submit the forms to a sharepoint site.  Due to an employee change recently we had to alter some of the data on the submitted forms so we did this using a SQL query rather than changing each form individual and on first glance when opening the form it seems to work but caused the error you described when trying to resubmit the existing forms after editing.  To resolve the problem, we can edit the forms xml file in notepad so that the data matches that in SQL server and the form then works again, but this then becomes a big job and we're back to modifying them individually again.  A similar thing could be happening to you.

    We were under the mistaken impression that creating a SQL main data connection would be just that, but it seems to use the XML file posted to sharepoint for more than just identifying the main SQL record.   If anyone has any suggestions, then they would be appreciated.

    Many thanks

    Tom

Page 1 of 1 (8 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.