>>Hmm... I don't know the problem, but I am curious. Why don't you use a parameterized view? Set the list box properties at runtime... then, if lnUserKey changes, you just requery the view, then requery the listbox? (or if you are using a .SCX form, you may not even need to requery the listbox)
>>
>>BOb
>
>Bob,
>
>This sort of "fun" may happen with view based combos too at the moment you destroy the bizobj. Depending of the order of instantiation, a combo might be requerying its view while the table on which the view is based upon has already been closed by the DataEnv.
>
I have found this to be true. So where do _you_ unhook the comboboxes from their rowsources to avoid this error?

>And while I am at it, what's your opinion about this one: how comes that setting AutoCloseTables in cDataEnv to .F. ends up with the same result as .T.? In both cases everything gets closed properly when you close the form.

Here's my 2 cents: From what I can remember at the moment, I think aDataEnv overloads the setting in cDataEnv. ReportEnvironments sets it to .F., Environment sets it to .T.

Cheryl

>
>José