>Actually, what I'm saying is to have the Database in the project - if you have stored procedures that are called from other code, it might get pulled in anyway - just don't use the database that's being shared with other people: use a local copy to isolate it better.
>
>That's interesting. I'm not sure why stored procedures being called would pull it in for recompiling purposes. Even if it did, wouldn't the building process use search DEFAULT then SEARCH PATH for the database? It sure seems to search the latter to resolve other file references when building (a major source of confusion in the past for me!!!)

That was just a guess, really - wrong, as it turned out.
If you have reference to a stored procedure elsewhere, you have to have the database to avoid compilation errors. The EXE will still build, however.
The build process won't look anywhere else except the project (or files in the project) for a stored procedure.