Jef and all,

One reason might be the fact that the classloc field in forms and classes cantain the relative path to used classlibraries.

When you have your classlibrary in a deep directory (IOW the relative path is long) this enlarges your executable because this path probably is occuring more than once in your exectable.

Let's say:
1. that you've a classlibrary containing one control.
2. You used this control from this classlibrary about 1000 times in your application
3. the relative path (eg. ..\..\..\myFramework\Myclasses\Myclass.vcx) contains about 100 characters.
4. you are able to place your classlib elsewhere so that the relative path now only contains 20 characters.

By doing so, you'll save 80 characters per used control. So for your whole project, you'll save about 80.000 bytes.

I suspect that by building an application from one machine, different relative paths are used to store in the application and therefore is different in size compare to the same application compiled from another machine.

If you open your application in notepad, you'll see the relative paths for aech visual class, forms and contained objects.

Its important to note that the execatuable itself does not need the paths to work properly. In an application you can either use:

1. DO FORM source\forms\Myform
2. DO FORM Myform

While it does matter if you try to run these from the command window (and do not have SET a PATH).

Walter,


>What are the possible reasons for building two two diffrent builds of exe files of same project on two seperate machines and having two different size exe files.
>
>Much Thanks
>Jeff