That makes sense with what I'm seeing. However a search of all drives results in only one VCX. I think the problem is that the EXE has a copy and there is one on the disk. At that point it seems to get confused.

There is something amiss. The project didn't have this problem in the past. Recent changes have brought it on. However, it is developed by a team and one member recently left. Otherwise I'd do the obvious and locate the change that made this start occuring.

>>Is anyone familiar with a problem when you SET CLASSLIB TO XX ADDITIVE and XX is already been set. I am getting the error "alias already in use". I can do this from the command line easily enough but it is failing in my EXE.
>
>Bud-
>
>This only happens when you try to SET CLASSLIB to another classlib with the same name as one that you have alreay set. Check that you do not have 2 copies of your library in your path.