>>>>What about the steps???
>>>>
>>>>>Windows 98 from the current MSDN set
>>>I deleted all entries in the watch window and that did the trick
>>>thanks to all who chimed in
>>>Peter
>>
>>
>>Hello all, If I may, I'm getting this error as well, but intermittently when my app is shuting down.
>>
>>I read earlier threads regarding this error and have tried the fixes regarding DCOM. I was able to track it down to an issue with datasessions.
>>
>>Specifically, I have a form that doesn't always release its private datasession. The datasession name in the dataview window changes to unknown(2), but does not release. Re-opening the form creates a new datasession. When the app shuts down, it crashes in the cusDatasession method of app_application (built with VFP60 app wizard). Okay, so here's the crazy part. I've been able to narrow this behavior down to when the form is opened and I use the navtoolbar to navigate to a record, then click a button on the form that executes some code and releases the form (using the releaseform method of the goapp object). If I click anywhere on the form before clicking the button, the datasession release okay and I get no error.
>>
>>Sorry if this is a bit long winded.
>>
>>Dean
>
>Playing with it some more, I realize the problem occurs when the navtoolbar was the last object click before clicking the button.
>
>Dean


Don't feel so bad. We have had to stay away from VFP 6.0 for certain projects because we get will get this error as well as a general VFP shutdown error when we execute a view that returns null values from a left join. We did a workaround by adding a value to one of the tables where the nulls were coming from that had a valid integer key but a blank field. The same pre-workaround view works fine in VFP 5.0 but no solution in 6.0. We let MS know but so far the bug has not made it to the documented category.

Bill