Since you are recompiling all, the database(s) are included in that compile, which means they need exclusive use.
You can recompile all your files manually - i.e., Compile progs\*
Compile Class Libs\*
Compile Form Forms\*
etc..

Or, you can build the project using a local copy of the dbc & tables and not the shared version.
It doesn't really matter that you use the shared version, as long as the structures are the same.

>I am having trouble building test versions of my app when the database it references (or tables in the data base) are in use by other people. As far as I can tell, none of the source files that reference the database do anything that would cause the database (or any contained .dbf) to be modified at build time, so I do not understand why I get a database access failure when trying to build a test version of my app during normal business hours.
>
>Here's the pertinent details:
>
>I build an .exe file for my project using the following Project Builder options:
>
>win 32 executable
>recompile all files
>display errors
>
>The Project Form shows two databases: the live (real) database and a test database. Both databases and all of the files contained in them are excluded from the build (a little exclusion icon appears to the left of each name in the
>DATA pageframe of the project form)..
>
>It is true that some of the forms in my project use the Dataenvironment and some tables from the live database are referenced in the dataenvironment of some forms.
>
>When I build the project, everything seems to go normally (the name of each prg file appears on the status bar as it is rebuilt, and so on....)
>
>Eventually, the builder displays the name of the live database on the status bar...as if it is 'building' it .... and if anyone happens to be using the database or a table it contains, the builder declares that access to the database is denied and stops the build process.
>
>This makes it extrememly inconvenient for me to build a test version of my app during normal business hours when the live database is in use.
>
>I do not understand why a build should desire write access to either of the databases referenced by other source files in the build if the databases (and their contained .dbf's) are not marked for inclusion in the build.
>
>Can anyone tell me why the builder wants write access to my databases and if there is any way to work around this fact so that I can build test versions of my app while users have database files open.