You're quite right about the "classic parallel sources pathology". We did have to put some rules into effect when we were developing. Now that we are well into the "Gee Barbara could you just add this little thing" we rarely have problems. We used Visual Source Safe, but lost more time to scrambled files than we had earlier to version control issues. So we made some ad hoc rules the group was willing to let me (as project manager) enforce. Herding cats comes to mind......

Don't know if VFP7 has improved this area, but I haven't seen it.

Barbara

>
>I'm sure responsible project managers have come up with all sorts of codified methods for working around the limitations of the project manager. You're method sounds like a good one but on the surface has the classic parallel sources pathology...which you no doubt have mitigated with some standardized maintenance procedures.
>
>Writing your own builder could help, but AFAICT, the real limitation lies in the limited resolution control one has over the 'compiler'.
>
>And, as I said to Trey, it sure would be nice, after you get a build, to be able to get feedback about all of the resolution results so you can easily detect when sources didn't come in from where you expected.
>
>Sure would save me a lot of time. 'H' file resolution has been especially problematic for me vis-a-vis FORMS and the fact that it's tedious to see how DEFINES have been resolved at debug time.
>
>I wonder if any of this has been improved in VFP7?