<?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: Viewset selection in TeamWork PLP or PLC? in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5771#M1126</link>
    <description>VERY IMPORTANT!&lt;BR /&gt;
&lt;BR /&gt;
The PLCs are essentially temporary backups and exist only so you can save without having to send and receive, and so you can continue to work when disconnected from the network.&lt;BR /&gt;
&lt;BR /&gt;
They can be used to create alternates by saving variations with the same sign in. In this case it would be appropriate to (temporarily) link the LBK to each PLC in turn to produce the alternate sets. This is a special case though, and the links should otherwise always be to the PLP.</description>
    <pubDate>Wed, 14 Jan 2004 23:03:18 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2004-01-14T23:03:18Z</dc:date>
    <item>
      <title>Viewset selection in TeamWork PLP or PLC?</title>
      <link>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5769#M1124</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;One of our clients is working on Mac with version 7.0 due to the speed issues. We advized them wait till at least version 8.1 before migrating the whole office to Panther with AC. They currently work a lot in TW and were wondering how to handle viewsets in the Layout books. Should they import  viewsets from the PLP or from the PLC files? &lt;BR /&gt;
What are the recommendations from all those experienced Mac 8.1 users out there? Our localized version of 8.1v1 is due later this month.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 May 2023 00:39:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5769#M1124</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-26T00:39:32Z</dc:date>
    </item>
    <item>
      <title>Re: Viewset selection in TeamWork PLP or PLC?</title>
      <link>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5770#M1125</link>
      <description>PLP, absolutely. &lt;BR /&gt;
&lt;BR /&gt;
The PLP file is the "real" file from which all others send &amp;amp; receive changes. The PLC files are just "working copies" which can vary from user to user.</description>
      <pubDate>Wed, 14 Jan 2004 16:32:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5770#M1125</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2004-01-14T16:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: Viewset selection in TeamWork PLP or PLC?</title>
      <link>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5771#M1126</link>
      <description>VERY IMPORTANT!&lt;BR /&gt;
&lt;BR /&gt;
The PLCs are essentially temporary backups and exist only so you can save without having to send and receive, and so you can continue to work when disconnected from the network.&lt;BR /&gt;
&lt;BR /&gt;
They can be used to create alternates by saving variations with the same sign in. In this case it would be appropriate to (temporarily) link the LBK to each PLC in turn to produce the alternate sets. This is a special case though, and the links should otherwise always be to the PLP.</description>
      <pubDate>Wed, 14 Jan 2004 23:03:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Viewset-selection-in-TeamWork-PLP-or-PLC/m-p/5771#M1126</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2004-01-14T23:03:18Z</dc:date>
    </item>
  </channel>
</rss>

