Hi Again,

Yeah, this makes sense. It is happening when you make parallel builds.

The main reason that we didn't experience this is because we used to build exes in a special build area. That is, all files necessary for the project were copied into a special build folder (with a special build VFP project.). I would recommend this approach.

This sounds more complicated than it really is. Especially if you are using something like visual sourcesafe that allows the files to be shared amongst projects. As well as having the different system projects in VSS, we would create a 'build' project in VSS for each system. This way, we could just get the latest version (updated files only) and make a build that way.

I take it that you are not using some version control software like Visual SourceSafe?

Mace


>Apologies, presses 'reply' to soon!
>
>Anyway to finish:
>
>This causes us problems because:
>
>It's quite large for a VCX
>The VCX memo file increases in size with each compile
>The recompilation process requires read-only access, which blocks compilation of other systems (often causes the infamous 'cannot update cursor' error.
>
>I hope that makes sense.