Generally: the more the better. But clients need far less RAM than do servers. For big applications or lots of users, the server will take advantage of all the RAM you can afford. Clients only need "big RAM" when using the Table View (Shift-F6) and when generating very large reports.

Also, you mention that Sesame needs to have a copy of the executable on every box. Sesame will run fine from a shared directory on a networked server. There is no need for a copy on every box. You can put the executable in a directory on your "file server" and share that directory without impinging on Sesame client/server or standalone operation.

Be very careful here, you are mixing client/server operation with file sharing of the executables. These are two very different things.

In client / server operation a copy of sesame is running on machine A. Sesame (no matter what hard drive it was read from) is running on machine B. A and B talk to each other about your application.

In file sharing, a copy of the Sesame executable is sitting on a harddrive on machine A. Machine B copies that executable through the network to its own memory and executes it on its own CPU.

Neither of these two models has any bearing on the other.

Quote:


The cost of file sharing Sesame executables is merely the time it takes to copy the executable through the network to your local CPU when Sesame first starts up. The benefit is that when you upgrade Sesame you only have to upgrade one computer - everyone else gets their copy from there always.

Quote:


Having fast graphics and a fast processor will enable the client's user interface to draw more quickly. Having a lot of memory will help with the Shift-F6 table view (or really super large table view subforms), and with generating large reports. Having a fast CPU on the client will help SBasic run faster and compile faster. But all of the really memory / CPU heavy operations (searching and sorting) are done by the server. If you watch client / server memory usage in task manager this becomes immediately obvious. The client will rarely exceed 10 Meg of memory usage. The server often need quite a bit more than that.

Quote:


Here is where client/server and file sharing are getting mixed together. The number of users sharing the same sesame executable will have little affect on the client/server performance. Client / Server performance will be based purely on the number of clients, the size of their applications, the speed of your network, and the operations they perform on the applications. This is true whether they are executing a copy of Sesame that is on their local harddrive, or are accessing a copy of the executable on a networked harddrive.