>1. Should I (a) install the entire app (.exe and database) on the server and have them all access the .exe from the network, OR should I (b) install the .exe on all local drives and have the database on the server.?
>
>If the answer is (b), I will need more info. How do I get the local .exe to point to the database on the network? What database issues exist on the network that are non-issues on local drives?

Rob,

I tend to keep both the .exe and data on the network drive. This lessens maintenence issues for the exe (updating it in one spot rather than many, etc.). Use your file server for what it is meant to do....

Sometimes, it is benificial to keep copies of the data on the workstations (which I discuss in the article mentioned below), but I am having a hard time coming up with reasons to keep the program locally (unless you can't be sure the network will always be up and running)...

Of course, you will still need to change your code so that it can handle multiple users. Any article on C/S development can be a good source for this. I have written an article for VFUG (October newsletter, I think) that discusses some methods. Just substitute "local view" for "remote view".... It comes down to buffering schemes and what you should do when multiple changes have affected the same data. The Pro's Talk book discusses these strategies as does Codebook 3.0 (in the beginning). There were some whitepapers (extracts from YAGs book) on the MS site as well, but since they randomly move thier documents around, I haven't found them lately....

HTH,
Scot.