This code checks for a previous instance of the program. This is not like the App.PrevInstance property. This checks the prevInstance no matter the location of the file, or the name of the app. You don't have to call DestroyWindow to destroy the created window, since when you quit the application, it is self destroyed. This may not work in the VB IDE, because the window is created by VB6.EXE. In this case you can call DestroyWindow in the Form_Unload().
Note: Due to the size or complexity of this submission, the author has submitted it as a .zip file to shorten your download time. Afterdownloading it, you will need a program like Winzip to decompress it.Virus note:All files are scanned once-a-day by Planet Source Code for viruses, but new viruses come
out every day, so no prevention program can catch 100% of them. For your own safety, please:
Re-scan downloaded files using your personal virus checker before using it.
NEVER, EVER run compiled files (.exe's, .ocx's, .dll's etc.)--only run source code.
Scan the source code with Minnow's Project Scanner
If you don't have a virus scanner, you can get one at many places on the net
including:McAfee.com
Terms of Agreement:
By using this code, you agree to the following terms...
You may use
this code in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
You MAY NOT redistribute this code (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
You may link to this code from another website, but ONLY if it is not wrapped in a frame.
You will abide by any additional copyright restrictions which the author may have placed in the code or code's description.
Great Work! It helps me a lot.....Continue to help PSC and other coders...5 Globes for the nice and very short module. (If this comment was disrespectful, please report it.)
dim Instance as long Instance =createwindow(etc....) then declare destroywindow and use destroywindow(Instance) in form unload although i was not smart enough to do that BEFORE i ran the code, so now i have that instancecode window that i can't kill.... i need to reboot to test the destroy (If this comment was disrespectful, please report it.)
Tom: In fact... No, you don't have to destroy the window, since it self destroys when the application is closed. That doesn't happen in the Visual Basic IDE, since the window was created by VB6.EXE, and not from your application. You can put the DestroyWindow API while you work in the VB IDE.
It will be the same to put it in Form_Unload() because if the application is closed by the Task Manager, Form_Unload wont be called. (If this comment was disrespectful, please report it.)
Nice idea. 5 from me. Will you see my method? It's on Id: 56211 . But I think this one is simpler. (If this comment was disrespectful, please report it.)
6/9/2005 8:21:27 AM:
Nice concise code and very useful - well done and thanks (If this comment was disrespectful, please report it.)
11/29/2006 4:24:51 AM:
very usefull code, great job! keep up good work! (If this comment was disrespectful, please report it.)
This solves the Previous Instance problem, which quit working in modern windows systems. It just works. (If this comment was disrespectful, please report it.)
Add Your Feedback
Your feedback will be posted below and an email sent to
the author. Please remember that the author was kind enough to
share this with you, so any criticisms must be stated politely, or they
will be deleted. (For feedback not related to this particular code, please
click here instead.)
By 7 Users
Download code
4/16/2005 6:03:52 PM: 
