Printable View
Microsoft (R) Incremental Linker Version 6.00.8168
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
LINK : fatal error LNK1104:
cannot open file "C:\Documents and Settings\Igor\Meus documentos\Meus Softwares\VB\VB6\OCX\EasyComponents\EasyComponents.ocx"
Any suggestions?
Does the file exist? Is it being used by another application at the time?
Yes, everything's all right. I've ever done this lots of times.
Happens that, altough it compiles normally, it shows this message in the end.
The worst is when I try to run the debug project to test my ocx.
I get a "permission denied" message everytime.
There's nothing unusual. I do these things since ever and then, I don't know why, neither microsoft does, apparently.
I checked my folders configurations, and all of them are marked as read only, and I can't change it. Maybe that's the problem, anyway, I don't know what's really happening. I thought that if I got to fix the compiler problem that would be all right, but now I see that there's a lot more.
Any ideas?
Well, from my experiences... If I have other VB instances running that are using the ocx, when I tried to recompile the ocx (opened in another VB instance), I'll get an error like you mentioned. I simply have to close previous VB instances and try again. At times, I'll even get the same or similar error you get. When this happens, I simply save my changes to the ocx project, close it, re-open it and re-compile it. If that scenario is true for you too; may just have to simply live with it. VB doesn't necessarily release all references to objects it creates (i.e., ocx, dlls) immediately when you stop running a project. It may keep them around for a bit until its garbage collection releases it or you close your project. That's my guess as to why I get those errors.
Bottom line suggestion: When you get that error, save your changes, close all instances of VB. Re-open your project and try re-compiling without making any further changes and hopefully the error is gone. Also, if you are using binary compatibility option, ensure the ocx you previously compiled is still there and not unregistered; otherwise, skip binary compatibility or reregister that previously compiled ocx.
It seems it was a firewall. And that read only stuff continues, but it didn't spoil my progress this time.
Anyway thanks for attention.
the file is lost!!Reset up:wave:Quote:
Originally Posted by ingoaglreen