You're not going be able to do things that way with COM components on multiple servers. You have to manage the versioning.


>Hello Craig/others;
>
>>There are two ways to do n-tier design. The first is logical, where each tier is separated, but all run on the same PC. The second is physical, where (typically) the UI runs on the desktop and the biz and data tiers run on servers.
>
>
> Right now, I have one application (a little) based on "Tasmanian Traders" sample.. Physically, I have .EXE (I almost don't make any change on it) pointing to many VCX libraries (at the end-users machines)
>
> There is some dificult to admin. the versions of each object.. On .EXE we can display on the form's caption (or about form) the number used on the last compilation..
>
> There is many different users at different places using that app... Some of them has 'that' so special modification others not..
>
> I was wondering, what about n-tiers applications.. How it can be well done admin. ? There is different slices of an app. shared between Server, Workstations, etc..
>
> How can be made the control of versions ?
>
>Tks
>
>Claudio