<?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 Re: Small gaps when cutting polygons after upgrading to 10.3 ArcDesktop in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471478#M26872</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any chance you happen to be running in a multi-user environment and not using versioning?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran into a similar thing when my folks were editing centerlines unversioned. If two people were editing and user A starts to make changes and user B makes a change and saved it before A could complete their change a database error or collision could occur. We didn't think too much of it until routing started failing and lines that were previously snapped together would no longer be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once we moved to versioning and no longer got the database contention errors things worked much smoother.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a thought&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Sep 2015 13:44:50 GMT</pubDate>
    <dc:creator>ThomasHoman</dc:creator>
    <dc:date>2015-09-11T13:44:50Z</dc:date>
    <item>
      <title>Small gaps when cutting polygons after upgrading to 10.3 ArcDesktop</title>
      <link>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471476#M26870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After updating to 10.3 arcdesktop users are experiencing small gaps when cutting polygons. See attached screenshots. I'm not sure if this is a settings change that needs to be made after upgrading&amp;nbsp; to 10.3? Any assistance greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Dec 2014 17:30:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471476#M26870</guid>
      <dc:creator>MarkMcGinnis</dc:creator>
      <dc:date>2014-12-22T17:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: Small gaps when cutting polygons after upgrading to 10.3 ArcDesktop</title>
      <link>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471477#M26871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been having the exact same problem since updating to 10.2.2 a few weeks ago and haven't been able to figure out why . . . &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Sep 2015 18:02:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471477#M26871</guid>
      <dc:creator>WillDeOreo1</dc:creator>
      <dc:date>2015-09-10T18:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Small gaps when cutting polygons after upgrading to 10.3 ArcDesktop</title>
      <link>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471478#M26872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any chance you happen to be running in a multi-user environment and not using versioning?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran into a similar thing when my folks were editing centerlines unversioned. If two people were editing and user A starts to make changes and user B makes a change and saved it before A could complete their change a database error or collision could occur. We didn't think too much of it until routing started failing and lines that were previously snapped together would no longer be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once we moved to versioning and no longer got the database contention errors things worked much smoother.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a thought&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Sep 2015 13:44:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/small-gaps-when-cutting-polygons-after-upgrading/m-p/471478#M26872</guid>
      <dc:creator>ThomasHoman</dc:creator>
      <dc:date>2015-09-11T13:44:50Z</dc:date>
    </item>
  </channel>
</rss>

