>>>Since I have upgraded my PC to Win2k, I now finds that I don't have any more instances of VFP 7 stuck in memory as I used to have under Win ME. By that, I mean, that even if no VFP instance was showing in the task bar, some were still residing in memory. Probably, this was due to not being closed properly. With Win2k, this has dissappeared. At least, after two weeks, I didn't get one so far.
>>
>>I recognize this for W95 and NT4 too (right now using W2K but the app closes all just properly all the way). Now what does it mean ?
>>Is it a pro or is it a con ? improperly closing just is not right; how will you know about it now ?
>>I was helped with it, because it really was wrong. I'd rather left it stay like that ...
>
>I'm not sure I understand what you're trying to say. To clarify, what I said what in reference that manually closing VFP in Win ME, sometimes, a reference was staying in memory. This never happened in Win2k. By manually closing, I mean exiting VFP with either Quit or other smooth mecanism. I didn't mean I was killing the app from the task manager.

Let me first tell you that your message wasn't in the list of messages since last global refresh (or so). So I had to find it via "get all the replies to your messages". Didn't see that before, but I guess that can happen.

Further, I interpreset your first Message as explaioned right now. So, by doing something wrongly, all forms have gone, but VFP.EXE is in the process list, and you have to kill it in order to start VFP again. Right ?
Your "sometimes" IMO is about doing something not neath, and all has gone except from VFP itself. And now I wonder : supposed W2K would kill VFP.EXE (as you state), is that a pro ? I'd rather see that I did something wrong.
I just don't like these kind of narrow escapes too much ...

But maybe that's not what you meant.