<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic IDataLayer Connect and Disconnect - Shapefile/GDB Locks in ArcObjects SDK Questions</title>
    <link>https://community.esri.com/t5/arcobjects-sdk-questions/idatalayer-connect-and-disconnect-shapefile-gdb/m-p/270418#M6923</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hey all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have an Add-In to "clip project area" essentially. Bunch of layers sourcing to multiple base data locations on our server, and this program basically says: select all features within extent, export, re-source layers to the exported location (the project folder).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question has to do with the pre-existing lock files to the original datasets. Even after the data has been re-sourced the lock remains. I understand lock files remain for some additional functionality (e.g. remove layer and then allowing the user to 'undo') but figured I'd double check with you guys first.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, is there any way at all, short of closing the MXD, to programatically remove these locks? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My thoughts were to try and implement IDataLayer.Disconnect, before re-sourcing the data, but that didn't work as intended.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any info would be appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Apr 2014 19:45:36 GMT</pubDate>
    <dc:creator>deleted-user-VeC5jUIlNXtq</dc:creator>
    <dc:date>2014-04-07T19:45:36Z</dc:date>
    <item>
      <title>IDataLayer Connect and Disconnect - Shapefile/GDB Locks</title>
      <link>https://community.esri.com/t5/arcobjects-sdk-questions/idatalayer-connect-and-disconnect-shapefile-gdb/m-p/270418#M6923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hey all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have an Add-In to "clip project area" essentially. Bunch of layers sourcing to multiple base data locations on our server, and this program basically says: select all features within extent, export, re-source layers to the exported location (the project folder).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question has to do with the pre-existing lock files to the original datasets. Even after the data has been re-sourced the lock remains. I understand lock files remain for some additional functionality (e.g. remove layer and then allowing the user to 'undo') but figured I'd double check with you guys first.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, is there any way at all, short of closing the MXD, to programatically remove these locks? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My thoughts were to try and implement IDataLayer.Disconnect, before re-sourcing the data, but that didn't work as intended.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any info would be appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Apr 2014 19:45:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcobjects-sdk-questions/idatalayer-connect-and-disconnect-shapefile-gdb/m-p/270418#M6923</guid>
      <dc:creator>deleted-user-VeC5jUIlNXtq</dc:creator>
      <dc:date>2014-04-07T19:45:36Z</dc:date>
    </item>
  </channel>
</rss>

