<p>
AKC is developed with the following tools
<ul>
<li>Aspire/J2EE
</li><li>Tomcat
</li><li>Java
</li><li>FrontPage
</li><li>Microsoft Access
</li><li>Borland JBuilder
</li>
</ul>
<h4>How long did it take to develop AKC?</h4>
<p>
At the time of this writing, I am talking about the Alpha release with all the functionality that you see now (June 2nd, 2003) it took me less than 2 weeks, from conception to deployment so that it is made available to the public.

<p>
In fact much of the time was spent in debugging sporadic network crawl which was finally traced to a faulty network card on the server and was duly replaced since then
<p>
I can't underplay the importance of any of the tools mentioned above, but the lion share of the system is developed with Aspire/J2EE (a collection of reusable java parts) and tested and deployed under Tomcat.

<h4>What do I need to deploy the system?</h4>
<ul>
<li>Tomcat 3.1 or higher
</li><li>Any tomcat supported JDK
</li><li>Microsoft Access (for now)
</li>
</ul>

<h4>Will AKC scale?</h4>
<p>There is always that fear about MicrosoftAccess not being a multi-user internet capable system. But so far Microsoft Access has been a great friend in enabling quick development. I am also sure it can handle decent loads. The only problem is a decent multi-threaded JDBC driver that can handle multiple connections. Because of this reason I may have to migrate to MySQL or SQL Server or Oracle at some point in the future.

<h4>How difficult is AKC to port to another Database?</h4>
<p>
It is quite easy. Aspire/J2EE keeps all SQL in external properties files. The microsoft access SQL being closer to ANSI SQL, this should be an easy process. Only possible hassle may be case sensitivity of the database objects. Again all of these are in external files.