<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Profitool on Fortran 2026</title>
    <link>https://fortran.sh3d.com.au/tags/profitool/</link>
    <description>Recent content in Profitool on Fortran 2026</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://fortran.sh3d.com.au/tags/profitool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Profitool</title>
      <link>https://fortran.sh3d.com.au/projects/profitool/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://fortran.sh3d.com.au/projects/profitool/</guid>
      <description>&lt;p&gt;We are experts on &lt;strong&gt;Profitool&lt;/strong&gt;, a long-running Fortran ERP. We have migrated a production Profitool deployment from 32-bit to 64-bit, added modern language features, and built the testing and deployment pipeline around it. If you run Profitool — or a similar Fortran-based ERP — we can take it forward instead of forcing you to start over.&lt;/p&gt;&#xA;&lt;h2 id=&#34;where-we-add-value&#34;&gt;Where we add value&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#where-we-add-value&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;32-bit to 64-bit migration&lt;/strong&gt; without losing decades of business logic — see &lt;a href=&#34;https://fortran.sh3d.com.au/expertise/migration-32-to-64/&#34;&gt;Expertise → 32 → 64-bit migration&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Modern extensions&lt;/strong&gt;: SQL database access, regular expressions, hash maps, and REST APIs added directly into the existing Fortran codebase.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Containers and reproducible builds&lt;/strong&gt; so the same binary you test is the binary you ship.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;A real test framework&lt;/strong&gt; — TAP-style unit tests with &lt;code&gt;prove&lt;/code&gt; runners, instead of &amp;ldquo;compile and pray&amp;rdquo;. See &lt;a href=&#34;https://fortran.sh3d.com.au/docs/unit/&#34;&gt;Examples → Unit Tests&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Day-to-day operations&lt;/strong&gt;: backup, restore, data recovery, and version-control discipline around a codebase that may have started before any of those existed.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;talk-to-us&#34;&gt;Talk to us&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#talk-to-us&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;mailto:simon@unisolve.com.au&#34;&gt;simon@unisolve.com.au&lt;/a&gt; or&#xA;&lt;a href=&#34;mailto:scottp@dd.com.au&#34;&gt;scottp@dd.com.au&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
