|
-
Oct 1st, 2009, 02:13 PM
#1
Thread Starter
Member
Re-directing where to look for Office library reference paths
I purchased Visual Studio 6 Pro Edition.
I installed it on a machine that has Office 2003.
I now need to reference the Excel 2000 library which is on another machine.
I can compile using a reference through my network to the Excel 2000 library, but if the machine I compiled on is NOT connected to the network, that compiled DLL fails to run properly. However, using that same DLL on machines other than on the one I compiled seems to work (that is the Excel library is found on the local machine -- at least the couple I've tried). I don't want the compiled DLL even attempting to look across the network for fear of delays and other network issues problems.
Is there a way to reference a library across a network but to have alternate paths specified in the source code which are to be used first by the compiled DLL before attempting to look over the network path?
If that is not possible, I worry that if I try to install VS6 also on my other machine, that it might invalidate the license for my present machine. Does anyone know whether I can install on two machines without causing problems with licenses?
Thanks in advance.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|