>Naomi,
>
>There's a difference between a compile error and the project unable to find all the components that you've told it that are supposed to be there.
>
>FWIW I don't see the exe size change by a single byte, with this main.prg:
>
>

>external procedure sp1
>
>open database testsp
>set database to testsp
>
>return sp1()
>
>* this is sp1:
>procedure sp1
>return 1
>

>
>between when the database is in the project and excluded and when the database has been removed from the project. When it's removed a build gripes, as well it should, in order to make sure that the exe isn't going to fail at runtime. Of course it can still fail if the code doesn't OPEN and SET DATABASE to make the SP available.
>
>But the exe is 24,332 bytes in size with or without the database in the project.
>
>>It's not enough, David.

David,

Thanks for running the test. I think there are two approaches here: ignore compilation errors (that's what we currently have) or include database and have 50Kb exe file increase (our database has a lot of SP), which is not a big deal...