The way I see it, I place a database onto a server on my network, i.e \\myserver1\myshareddir\mydatabase.mdb then get each application on different computers to access that database. Does this work? and is it the best way?
It depends - how many is a "bunch" of computers? Often MS Access isn't good for many simultaneous users and Microsoft recommends against many users. It also depends on types of interaction with the database - a bunch of free form queries?...or a "canned" set of forms for data entry.
The simple way you describe could be a performance nightmare since the data-engine is local and the data remote. This causes alot of network traffic. I think you may need to split the database in two - a front end DB on the client machine and the backend DB on the server. Check out microsoft.public.access.multiuser
thanks bill, in the end that's exactly what I went with. A frontend and back db. I weighed it all out, and since there are other databases running with other preexisting programs, the bandwidth of the network seemed like it could use some slack.