Rob, you can have it either way having a copy of the exe on each computer - is a little faster obviously as for pointing tho the table wither use UNC names or mapping or stored in INI, REgistry etc. to tell the app where to find the data (SET PATH etc.) note however that the more complicated issues of having a newtwork app are the record locking , buffering and handling priority issues ets e.g. what happens if two users send updates to the same record Arnon > > I have an application that is used by several customers around Chicago. > They all are single users on local hard drives. My next potential customer > wants to run my app on a network. I have a few questions about this. > > 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? > > If nothing else, maybe someone out there knows of a book or online resource > that outlines the entire process of installing a VFP app onto a network. > > Thanks, > > Rob Csenar >