Releasing lock on file - InfoPath Dev
in

InfoPath Dev

Releasing lock on file

Last post 07-17-2008 06:06 AM by komgal. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 12-08-2005 03:46 PM

    Releasing lock on file

    I need InfoPath to release the lock on a file without actually closing infopath.

    My users use InfoPath to edit XML files. They want to view these files in a browser at the same time... Side-by-side.

    Except once you save changes in InfoPath, InfoPath takes an exclusive lock on the file and nothing else can read the changes.

    Is there any way to convince InfoPath to either not lock the file, or at least release the file without closing the app/doc?

    Thanks,

    -Mark

  • 12-09-2005 07:05 AM In reply to

    Hi,

    Sorry but I don't think that is possible Infopath lock his files when he is open! It's rules for that the user can't modify it and make trouble!

    Imagine that your user modify the xml infopath crash in all the case! I know that you wan't only see it!
    What you can do is a button that send an image of your xml at this time!

    or you can make a each change an onafterchange event that send the xml file in a webseervice and generate an aspx page that reload every times that the webservice is call!

    But if you want to see the template.xml in each second you can forget!

    ++

    Thierry
    Infopath 2007, Langage: C#2.0 (Modèle Objet 2003)
    merci de lire ceci
  • 12-09-2005 07:07 AM In reply to

    I don't understand; why are you using InfoPath to edit XML?

    ---------------
    Matt Faus
    Matt Faus / Microsoft InfoPath MVP
    Qdabra® Software / Streamline data gathering to turn process into knowledge
  • 12-09-2005 09:04 AM In reply to

    Matt,
    Isn't that what InfoPath is for? (sincere question) I mean it's a data editor, and XML is data. I have users that need to edit the data but have no experience with editing XML.

    Is there a better "super-friendly" editor for XML?

    The big picture is that the XML files contain structured "content." This content is created/edited by typists, not geeks. The content is stored as XML and then transformed with XSLT so that it can be viewed in a browser. Storing the content in XML allows us to completely separate the content from the design.

    The fact that the editors can't quickly switch back and see their rendered content without closing Infopath is the only major flaw in our otherwise well-executed plan of making this part of the job easier.

    I would be thrilled if there were a button in InfoPath to "Release" the lock... sort of like the "Apply" button we see on windows dialogs.

    -Mark
  • 12-09-2005 09:37 AM In reply to

    Ok, now I see. When you said "edit XML files" I thought you meant you were reading in a file, displaying it in a textbox field on an InfoPath form, having users edit the raw XML and trying to save it back out. Nevermind, haha.



    ---------------
    Matt Faus
    Matt Faus / Microsoft InfoPath MVP
    Qdabra® Software / Streamline data gathering to turn process into knowledge
  • 07-17-2008 06:06 AM In reply to

    • komgal
    • Not Ranked
    • Joined on 11-14-2007
    • Posts 8

    Anybody found a way how to release exclusive lock without closing Infopath.

    Will appreciate any ideas or maybe custom code? Thanks

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