Need help with a possible Varible/Memory problem

[Magnum357jhp]

I'm working on a project that is not directly related to Truevision.  I think I may know the problem, but not sure how to fix it.  I built this program, a prototype game, that uses a lot of Varibles in VB6, but when I try to delete the program from the computer, I get the following message...

<ERROR DELETING FILE>

Can not delete <file>: Access Denied.
Make sure the disk in not full or Write-protected and that the file is not currently in use.

If I reboot the computer, it allows me to delete the program easily.  I'm guessing the problem I'm having is that the Varibles and perhaps the VB6 program itself is still being used by Windows and that I need to "unload" the varibles from Memory, but I'm not quite sure how to do that.  I know in Truevision, its a good idea to "Unload" the Truevision file, but does anyone have any advice on how to do this with just simple VB6 programs? 

Any info would be most apprecated.

[Lordtek]

1. Don't use doevents when working with files if it can be helped because the buffer can get pretty full and a lot of stuff will be waiting to be written if you close the program before the file closes.

2. close all the files in the form unload sub

3. "end" the program in the form unload sub

[Magnum357jhp]

Ok, I think I get what you mean.  But how do you "End" a VB6 program?  I have quite a few varibles in this program (and I assuem taking up the buffere space) how do you unload all those varibles?   Is there a simple command line I can use to unload everything, or do I need to "end/unload" each and every varible? 

Also, the program does use a Database file, if I need to unload anything here aswell, does anyone got any advice on Database accessing?

[Lordtek]

The standard variables will be reclaimed when you "END" the program but if you have variable made with set/let you have to manually set/let them = "NOTHING". As far as the database file goes it is really wise to manually close these files as well. I have found a few data base/grid OCXes (is that a word???) provided by Mr. Bill and Co. to leak horribly if you don't manually unload them from the ocx but if its a home grown db just close it and its done.