>>That's VFP 6.0. This was in reponse to a question about VFP 5.0. I've never seen this sort of behavior in 5.0, unless I've done something wrong. I don't have a problem with admitting that there's a problem with VFP 6.0 when IE 4.01 isn't installed or DCOM98 isn't.
>>
>
>Your right... VFP 5.0 says the subject line...
>
>>In working with VFP 6.0, I haven't seen this. I only know what's been reported here. Of course, I've got IE 4.01 installed, so that may be the reason. I have gotten this error, but it was something I did. Like I said, I don't have a problem with admitting when there's a problem with the product. Neither do I have a problem admitting my own mistakes.
>>
>
>I do have 4.01 SP1 installed.
>
>
>>I understand your frustration.
>
>Thanks... didn't mean to snap at you.
>
Hi BOb,

Wasn't taken that way. I was simply trying to post my experiences in the matter. Unfortunately, sometimes the sequence of events that occurs is: 1. Program GPFs, 2. Programmer immediately blames it on product bug. Until I can prove otherwise, I always blame myself. Too often I've done something incredibly stupid that blows up VFP.:-)

I will say one other thing in reference to my environment that might make a difference. I'm using Win98.

Hope you get the problem resolved.

Regards,