Vincent,
From reading your posts, it's obvious you are quite knowledgeable about computers. But, I am not quite sure what you define as a Client-Server application. Sure, the best example of client-server is a browser (client) and a web site (server), but there are many examples of client-servers and a classis is the LAN or WAN. The local area network is what would most likely be used by users of AC. A server-client is best defined as when a client requests information from a server, and the server sends that information back to the client. On a local area network clients and AC can send info to the database as well. Client-Server relationships can even exist on one machine.
AmazingCharts can easily be used in a peer-to-peer environment where all computers are virtually equal and share files and the AC databases with each other -- the AC database HOPEFULLY residing on one PC. We, however, have a client-server environment. We set up the databases on the server and the client versions request and send data to the server.
Our overall setup is very simple. ISP to Cisco PIX Firewall/Router to a Linksys Gigabit switch with Cat 6 cable connected centrally to a Small Business Serve 2003 server. Again, while one can certainly run AC in a peer-to-peer environment, utilizing a server allows the program to run faster and more securely. In a peer-to-peer environment all users are dependent on the computer which may be being used as a workstation which would slow it down or allow more freezes or crashes require reboots, where a server can run unattended for days to weeks without crashes, etc.
Certainly setting up your LAN with static vs dynamic IP addresses is a personal choice, we tend to use a static IP address for our outside interface, the router and the server and allow the server to be our DHCP. While the LAN will work either way, in a true domain network, it is simpler and generally more efficent to allow the server to set IP address, subnets, gateway, DNS, domain names and WINS.
