JAC,
You need the Access Developer Extensions that now are part of the Visual
Studio Tools software to save a file for use without Access. As to the
server, multi-user applications should be split into two databases--one that
has only the tables (the backend), and one that has everything else (the
frontend). The backend is stored on a network server while each user stores
the frontend on his local hard drive.
This structure minimizes network traffic by allowing form, query, and report
definitiuons, and code, to be uploaded locally rather than across the
network. From a developer point-of-view, it also makes upgrades to the
database, which are nearly always new and/or improved forms, changes to code,
new/better reports, etc. to be done without having exclusive use of the
database.
You should be aware, though, that while Access handles many multiuser issues
"behind the scenes", there are other aspects that the programmer must handle,
including record-locking strategy, error-handling, security, etc. I strongly
advise reading up on these issues or looking into hiring a professional
Access developer. The Access Enterprise Developer's Handbook by Litwin et al
covers these issues well.
Hope that helps.
Sprinks