VB and dll's
- From: NYTRA <nytra@xxxxxxxx>
- Date: Thu, 13 Jul 2006 13:09:37 GMT
Hello,
I have a question regarding how VB calls dll files and loads/unloads them from memory. If this isn't the correct forum, please point me to the correct one. I'm not really a programmer, please forgive me if I don't know what I'm doing. :)
That being said, we have an app that was written in VB that loads a number of dll's. After a period of inactivity in the program (maybe about 10 minutes) some of these dll's unload. Not all, but most of them. This is causing significant delays within the app when the dll's need to be reloaded.
This is what the software vendor says regarding the way the dll's they created behave:
Objects are closed (or destroyed) under the sole control of Windows.
Windows holds objects in memory in case they need to be used again. If
an object is not needed for period of time or the system runs low on
resources the object is closed to free up space for active processes.
My question is, is there a way to make particular dll's stay open until the program is closed? I would like to have them all load and stay loaded, not just close on their own.
BTW, the system running low on resources is not an issue.
Thanks,
Walt
.
- Follow-Ups:
- Re: VB and dll's
- From: Karl E. Peterson
- Re: VB and dll's
- From: expvb
- Re: VB and dll's
- Prev by Date: Re: Automating sending e-mail
- Next by Date: Re: vb6 bcoming irrelevant?
- Previous by thread: Comments/education VB6 limitations?
- Next by thread: Re: VB and dll's
- Index(es):
Relevant Pages
|