dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Visual Basic
Expertise: Beginner
May 3, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Unloading Application from Memory

Question:
I have written an application that uses both DAO and OLE calls. This is a form-based application that sits on top of a CAD package. Sometimes when a user exits the application, the application stays resident in memory (for example, it shows up in the task manager). I am fairly sure that I am releasing all of my DAO and OLE objects. What might be causing the problem?

Answer:
Make sure that all forms are being unloaded, and that in the Unload event of the last form to be unloaded, you have the End statement. If you don't End the application, you can get a phantom app with no windows that keeps running.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date