This problem is not limited to any specific framework. You are right in determining that the problem is related to the combobox. VFP6 is actually worse (I think) about this than in 5. The problem is not the requery, but the fact that there seems to be some sort of refresh going on as the form is destroyed.

This problem only occurs when the rowsourcetype is Alias or Table. One way to eliminate is to use RowSourceType=3 - SQL. This never generates this error because the combo is bound to a cursor of it's own that gets closed when the data session ends.

If you can't do that, then you may have to programatically unbind the combobox when the form releases. Sometimes you can do it in the Destroy event of the combobox but occasionaly this hasn't worked either, or produced inconsistent results.

Hope this helps.

>Hi all,
>
>This error has been a nagging one, that I finally think I have figured out. I have been receiving this error when closing forms subclassed from cBizObjForm. It doesn't happen all the time. Here is what I have figured out:
>
>The framework releases business objects placed on the form before doing anything else. It then relies on VFP to release all other objects on the form in reverse order than they were instantiated.
>
>This means that the data (views) are closed before the objects on the form (textbox, combobox, etc.) are released! This sounds like it could potentially cause this error, if for some reason an object requeries its rowsource or controlsource.
>
>Next I started fooling around with a test form to reproduce it. I couldn't reproduce it until I placed a combobox on the form. The error would occur for every combobox I placed on the form! More testing revealed that somehow, the combobox was requering its rowsource. I am not doing this programmatically, and neither is the framework. I turned event tracking on, and the combo's requery never fires.
>
>So, I'm not sure why the combo is requering its rowsource, but that definitely looks like what is happening.
>
>BTW, I am using version 3.02 of the framework right now.
>
>Any comments/suggestions would be very appreciated.