David,
We have two projects - identical except that one has the database in it (for everyday programming, review, etc.) and the other does not have the database. Compiling is a breeze, and because the projects are O3 and O3b the compiling always results in a file O3b.exe which we can test without overwriting the 'working' file. When we're sure of the changes, we do a 'hot swap' renaming O3.exe to O3_yymmdd.exe and O3b.exe to O3.exe. The next time each user opens the program our 'wrapper' copies the new version onto his local drive.

Multiple project files also gets around the problem of a programmer not being able to open a project because it's in use by someone else.

>Thanks for the timely responses.
>
>Trey and Dan seem to be saying roughly the same thing. To wit...
>
>"Don't let the project builder see the database at all since it really isn't used in the build."
>
>Still, even though I do not include the live database in my project, it sure is convenient to have it there for quick and easy access to database files when I need to reference them from time to time.
>
>I suppose I could create a 'Database' project which only contains my databases. I could keep this project on the desktop, pushed out of the way, while I work on my real project. Then, as the need arises, open up the 'Database' project to access .dbf files as needed.
>
>I'll try this approach for awhile to see how it works.