>>>>>I am wondering if there is a reason, why an exe that is compiled on another workstation, but from identical source code, may have a slightly different size? In this case, the total size is around 56 MB, but the files differ with arund 400 bytes. If the size would have been identical we could rely on the fact that the compiled executables are the same.
>>>>
>>>>My guess would be that the project file contains paths to the project and if you're building in different folders on the two machines you're going to have different paths in there. When you build in a new folder you typically get asked by the PM if you want to make the new folder the project home folder and that path goes into the project and is updated in several places.
>>>>
>>>>+++ Rick ---
>>>
>>>I believe you are correct, it is the most likely reason. Monday I will test again.
>>
>>Yes, forgot this reason. Happened to me.
>>
>>There are 2 solutions for this:
>>- Force that everyone use the same directory structure on their HDs
>>- Use an automation building server for preparing the EXEs (we did use CruiseControl, now using Ágora with Jenkins)
>>
>>Best Regards.-
>
>Yes that is a good idea. Although the executable may be the same, if the size would vary for the same version, the client's may doubt the integrity of our procedures.
>
>That is why we are now also thinking about a separate build process, instead from the development source, to checkout from svn and build from a separate copy.

Christian, I see that, despite there are many new SCM/DVCS tools for using with VFP 9 (Git, PlasticSCM, Perforce, Mercurial, ...), you keep using SVN.

How is your team dealing with the diff and merges of the code (forms, classlibs, etc)?