>How do you tell VFP to NOT scan the project looking for dependencies that it then automatically adds to the project?
>
>If you have one class or reference in the wrong place and you try to build a small little project VFP ends up finding that reference and ends up pulling code from other projects into this project. It's very handy behavior most of the time, but sometimes it's a giant PIA.

That's one of the major reasons I recommend not putting multiple udfs/procedures into .PRGs nor multiple classes into a single classlib. Seriously, think about it this way - the blueprints for a car, do not get sold with the car. Our work is all blue prints. The final exe does not care how the source is organized.

By having a library.prg with several routines in it, when you need 1 routine, the whole thing gets built into the exe/car. Who thinks that's wise/practical regardless of the "that's the way we've always done it".