Reference an AxtiveX dll project in another project

Hi,

I know this sounds crazy but it happened and I have no idea about it. If anyone can give me some hint I really appreciate it.

I have several ActiveX Dll projects which I reference in other projects. They are all in the same group. At the beginning when I set these up, perfect, no problem. Everytime I compile the project group, I just do it. If I modified the source of the dlls, I can compile them with no problem.

After several days using the project group, Suddenly this annoying "permission denied drive:\path\anything.dll" pops up. So I thought I might reference the dll by the dll name, not the vbp name. So I checked the settings but they are right. The rediculous thing is It only happens if I want to compile one particular dll. Other dll projects are good as before. More funny thing is, if I close the project group and reopen it, it let me compile again. Then I make changes then the annoying thing pops up. Then I have to close the project group and reopen.

Any one has any ideas? Tons of thanks.

ordnance,

Yes, strange thing happen in the IDE when your program does not release objects and memory properly when it is run. When this happens the IDE is unaware of these problems and sooner or later something bad will happen. Most often is you cannot compile.

When you restart the IDE the memory and objects are released and you are able to compile again.

Quote:

---

Originally Posted by randem

ordnance,

Yes, strange thing happen in the IDE when your program does not release objects and memory properly when it is run. When this happens the IDE is unaware of these problems and sooner or later something bad will happen. Most often is you cannot compile.

When you restart the IDE the memory and objects are released and you are able to compile again.

---

Thanks randem, but this doesn't seems to be the case. When I restart the IDE, I can compile only once. When I try to compile it again, it doesn't let me. I don't even necessarily run the program yet. Any ideas?

Notice randem mentioned releasing objects to clear memory. You may need to go over your programs code and check if objects are created and not cleared. IE:

VB Code:

Set object = Nothing
'or
Unload Object

Etc..

Phreak

Well, finally I did this. I removed the project that referenced the dll and recreated the project. Then I set up everything again and it works. Just don't know how long it will last. Thanks for your help.

This is normal for the VB IDE. I have come to expect this when making my own Controls, usually .OCX objects