Printable View
I get the above message when attempting to re-compile an ActiveX DLL and overwriting the file that I am also maintaining binary compatability with.
I do exactly the same thing with many other ActiveX components without any problem so it onl affects this DLL.
When I click on 'View error messages', it displays the following error:
Has anyone encountered this before?Quote:
LINK : fatal error LNK1104: cannot open file
"\\EX1\LANROOT\Compiled\Components\ecsPostCodeLookup.dll"
seems to me that there is a problem in the project. Create a new project cut and paste your code from the existing project and that should do it. Else if you can it may be worth unregistering and deleting the existing DLL (if you can), set the current project back to 'No compatiability' and compile.
I will try what you have suggested but it is a new project and this started happening the first time I attempted to re-compile it.
I looked through the Microsoft knowlege base for related articles and found one article that said Microsoft were aware of this problem but did not know why it occurred but were looking into it.
The knowlege base article can be found at:
http://support.microsoft.com/support...-GB&SD=gn&FR=0
it's so Old Subject . LOL but i also Face the same problem:
Microsoft (R) Incremental Linker Version 6.00.8447
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
LINK : fatal error LNK1181: cannot open input file "E:\Program Files\Microsoft Visual Studio\VB98\VBAEXE6.LIB"
and i went to Microsoft there is no SOLUTION
But i Check my File VBAEXE6.LIB it was not there
So i just search the CD and found the File Finally copied it in the Dir ... Fixed the Problem
Sorry for my Bad English
Looks like the DLL was compiled/registered on a LAN share. In order to preserver binary compatibility, the IDE must locate and interrogate the original file. If the file was registered on a LAN share that no longer exists, I could see this happenning.
Do a REGSVR32.EXE -U on the DLL, then register it again in the %systemroot% and then try it.
lol love those 4-year-old posts that pop up.
I've had the same problem numerous times. I think it has something to do with the ODL reflection inside the VB IDE!
Although MS method works well most of the time, there will be a time where you're going to need to turn of binary compatibility and regenerate all those CLSIDS,GUIDS etc.
. . . and recompile every dependent project.
Yuk!