<?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>idea arcpy.TestSchemaLock() should be able to check workspace in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-testschemalock-should-be-able-to-check/idi-p/953210</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;The function arcpy.TestSchemaLock() takes as input a dataset for which it returns TRUE or FALSE depending if a schema lock is in place. This works great for a Table or FeatureClass but it needs to be able to test a workspace, specifically a personal geodatabase. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unless ESRI plan to drop all support for a personal geodatabase (which they have done for ArcGIS Pro) then it would be a simple and effective improvement on this function if it was able to take a dataset OR a Workspace and return the boolean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have scripts that write to personal geodatabases and these can very easily get locked by another application or user. You could argue that I should be writing to a file geodatabase but there are good reasons for wanting to write to a personal geodatabase.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jul 2016 11:51:06 GMT</pubDate>
    <dc:creator>DuncanHornby</dc:creator>
    <dc:date>2016-07-19T11:51:06Z</dc:date>
    <item>
      <title>arcpy.TestSchemaLock() should be able to check workspace</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-testschemalock-should-be-able-to-check/idi-p/953210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;The function arcpy.TestSchemaLock() takes as input a dataset for which it returns TRUE or FALSE depending if a schema lock is in place. This works great for a Table or FeatureClass but it needs to be able to test a workspace, specifically a personal geodatabase. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unless ESRI plan to drop all support for a personal geodatabase (which they have done for ArcGIS Pro) then it would be a simple and effective improvement on this function if it was able to take a dataset OR a Workspace and return the boolean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have scripts that write to personal geodatabases and these can very easily get locked by another application or user. You could argue that I should be writing to a file geodatabase but there are good reasons for wanting to write to a personal geodatabase.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jul 2016 11:51:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-testschemalock-should-be-able-to-check/idi-p/953210</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2016-07-19T11:51:06Z</dc:date>
    </item>
    <item>
      <title>Re: arcpy.TestSchemaLock() should be able to check workspace</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-testschemalock-should-be-able-to-check/idc-p/1610560#M34647</link>
      <description>&lt;P&gt;Thanks for the idea. But as mentioned in the original post ArcGIS Pro does not support personal geodatabase.&lt;/P&gt;&lt;P&gt;We're planning to close this issue shortly.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 18:35:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-testschemalock-should-be-able-to-check/idc-p/1610560#M34647</guid>
      <dc:creator>gprince</dc:creator>
      <dc:date>2025-04-30T18:35:13Z</dc:date>
    </item>
  </channel>
</rss>

