mmm....
I installed W2KP 3 weeks ago and I've had to reboot only once, when apps suddenly refused to run any more. Nothing peculiar happened prior to that problem.

Since installing W2K I've had IE blow up several times, NS do that same, and even VFP in the developer mode has barfed a lung on a couple of occasions, but none of these events forced me to reboot W2K. My box is up 24/7 and does nightly backups of mission critical apps. My co-worker installed W2K a week ago and has had only one crash. Considering how many times W98SE was laying down on the job, W2K is a breath of fresh air. In fact, had Win95 displayed such stability three years ago I wouldn't have bothered to look for a different OS to put on my home box. I know what you're thinking!! Too late! I'm a dedicated Penquinista now! :) In fact, we've already got a SuSE 6.4 serving up tax info 24/7 since last September, without a single crash! Surely, with such and stellar and economic record, more incursions will follow.

But, if Gates & Co. will just lay off the bells & whistles pile-on for a while, and increase stability and security on W2K, and not get so greedy and restrictive on the licenseing, then maybe Linux wouldn't .... naa, that's expecting too much. Besides Linux is too much fun and the TCO is unbeatable.
JLK

>>>The only way to ensure that I do not get another C5 error is to restart Windows 2000.
>>>
>>>This seems counter-intuitive to me. Why does VFP not start with a clean slate?
>>>
>>>Peter Robinson
>>
>>Which service pack for VFP are you running? I'm running SP4, and I don't have this problem.
>
>I'm running VFP 5.0 with SP3. I'm sure you are running VFP 6.0 and I suppose that is one of the reasons I am asking. It makes sense that VFP 6.0 would play better with Win2K.
>
>I still think that VFP, regardless of version, should start with a clean slate.
>
>Thanks for answering.
>
>Peter