<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">
    
    <channel>
    
    <title>Trigram Software</title>
    <link>http://www.trigram.com/forums/</link>
    <description>Trigram Software</description>
    <dc:language>en</dc:language>
    <dc:rights>Copyright 2007</dc:rights>
    <dc:date>2007-12-19T06:55:04-08:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <item>
      <title>Issues with update process; please advise</title>
      <link>http://www.trigram.com/forums/viewthread/9/</link>
      <guid>http://www.trigram.com/forums/viewthread/9/#When:16:09:17Z</guid>
      <description>&lt;p&gt;Greetings.
&lt;/p&gt;
&lt;p&gt;
I am updating AcuBase Pro using the instructions at the PDF at &lt;a href=&quot;http://www.trigram.com/downloads/AcubaseUpdateInstructions.pdf&quot;&gt;http://www.trigram.com/downloads/AcubaseUpdateInstructions.pdf&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
I believe the version that i&#8217;m updating from is incompatible with these instructions.
&lt;br /&gt;
The three files named acubasepro.usr, acubasecalendar.usr, and logfile.usr appear to be not present on my disk and there is no &#8220;Update&#8221; folder.
&lt;/p&gt;
&lt;p&gt;
I do not observe any way to find the version number from within the program; I can&#8217;t see a scripts menu as the docs describe. There is no password upon loading.
&lt;/p&gt;
&lt;p&gt;
Do you have any advice for me?
&lt;/p&gt;</description>
      <dc:date>2007-12-17T16:09:17-08:00</dc:date>
    </item>

    <item>
      <title>How to upgrade from a single&#45;user version to a network version of AcuBase Pro</title>
      <link>http://www.trigram.com/forums/viewthread/7/</link>
      <guid>http://www.trigram.com/forums/viewthread/7/#When:19:47:09Z</guid>
      <description>&lt;p&gt;This is a question we often get.&amp;nbsp; I&#8217;ll post from an email below&#8230;
&lt;/p&gt;
&lt;p&gt;
    1) Can we just pay the difference from our Single Computer license to upgrade to the Small Network license? So we could pay the extra $300 to upgrade? (We purchased the Single Computer recently).
&lt;/p&gt;

&lt;p&gt;
Yes, we can work that out, pro&#45;rate the difference. 
&lt;br /&gt;
 
&lt;/p&gt;
&lt;p&gt;
     
&lt;br /&gt;
    2) How does switching from a Single to a Small Network version of Acubase work? We have some data set up in our current one and would like to port it over. Is that difficult?
&lt;/p&gt;

&lt;p&gt;
We can help you set it up.&amp;nbsp; The easiest way would be if you bought FileMaker Pro (currently the regular version, 9.0:&amp;nbsp; &lt;a href=&quot;https://store.filemaker.com/product/viewfamily/family/FMP&quot;&gt;https://store.filemaker.com/product/viewfamily/family/FMP&lt;/a&gt;).&amp;nbsp; You need to buy one copy for each machine on which you wish to use the program. Then we&#8217;ll give you a new license number so you can make AcuBase a network version, convert your current AcuBase file to a FileMaker file, and set it up on whichever computer you consider the &#8216;main&#8217; (server) computer. 
&lt;/p&gt;
&lt;p&gt;
The way the network version runs is that you will open the AcuBase file in FileMaker on the server machine.&amp;nbsp; To open it on other machines, open FileMaker, and go to File/Open Remote and open it through the network. The AcuBase file only needs to be (open) on one machine, and the others see it through FileMaker.
&lt;br /&gt;
 
&lt;br /&gt;
Backup&#45;wise, it&#8217;s the same file structure as your current version: it backs up to a Backup folder on the server machine (inside the AcuBase Pro directory where the other AcuBase files are located), and you need to move that to an off&#45;site backup every so often for further data security.
&lt;/p&gt;</description>
      <dc:date>2007-12-03T19:47:09-08:00</dc:date>
    </item>

    
    </channel>
</rss>