G
Guest
In Word O2K, XP, 2003, is there a way to avoid the hassles of orphaned
References?
For example: I have created a DOT file on a development workstation. I have
added several custom DLL references. Each of these references should be in
the same place on the production workstations, but sometimes they are not.
Keep in mind, all of the DLL files are registered on the production
workstations.
If I go to a workstation that does not have the DLL files in the same place
as the development workstation, the DOT file will fail.
Is there a way to avoid references based on file locations and only rely on
the registry? So if my development workstation thinks the files sit in
C:\Temp1 but the production workstations think the files are in C:\Temp2 I
would like my DOT to acknowledge the new location and just use those files
in C:\Temp2. Is this possible?
I would just include the DLL files in my install package and place them in a
specific folder, but these DLLs are part of a bigger package that is already
installed on the workstations.
Thank you!
Doug
References?
For example: I have created a DOT file on a development workstation. I have
added several custom DLL references. Each of these references should be in
the same place on the production workstations, but sometimes they are not.
Keep in mind, all of the DLL files are registered on the production
workstations.
If I go to a workstation that does not have the DLL files in the same place
as the development workstation, the DOT file will fail.
Is there a way to avoid references based on file locations and only rely on
the registry? So if my development workstation thinks the files sit in
C:\Temp1 but the production workstations think the files are in C:\Temp2 I
would like my DOT to acknowledge the new location and just use those files
in C:\Temp2. Is this possible?
I would just include the DLL files in my install package and place them in a
specific folder, but these DLLs are part of a bigger package that is already
installed on the workstations.
Thank you!
Doug