Bert,
The term "Client-Server" when referring to computer network applications has a very definite meaning - one in which there is a server-side application running to assist the client-side application. An example is a database server handling data requests for an application, rather than processing the actual data files from a file server over the network. Generally, client-server applications require much less network traffic, as instead of multiple remote file reads to find a piece of data, a single request is sent to the server application, and a single answer to that request is sent back.
That being said, Amazing Charts is a shared database application, and indeed the data files have to reside on one computer. One thing to consider, though, is that the needs of a file server are much different than the needs of a workstation. A workstation is configured to run applications as fast and efficiently as possible, and sharing data back with the network is a relatively low priority.
A file server, on the other hand, is configured to handle requests for data from the network as quickly. Even so, it is still serving disc file reads, and this does not make this environment "client-server"
Technically my network is "peer to peer", with my dedicated linux-powered file server being a very fast peer sharing files. While they are indeed clients, and you indeed have a server - this is NOT a "client-server" application environment.
Clear as mud yet? lol
We use static IP addressing for our servers and our remote-controllable clients as we remote access them and most low-end routers have a nasty habit of randomly re-assigning IP addresses as DHCP leases expire. We route VNC requests for remote desktop, IPP requests to appropriate printers, and inbound requests to the security camera on our webserver through static routes.
We COULD of course disable the DHCP server on the router and enable the DHCP demon on our main server, which probably wouldn't have that problem, but for now static IP addressing works just fine.
V.
