>As soon as I sent you my previous message I thought about the same. Why not to do all this business in the container INIT method. And then from the INIT method to .Requery() the combo.
>
>Thank you very much for the suggestion. It should work.

Exactly the technique I've found useful in several situations. Doing something to combo's rowsource (or creating it) in combo's .init() is not really nice, because it happens only once, and actually belongs to .requery(). If it relies on entities which will exist later, well, call it later. The upside of this is that the code is in combo's .requery() where it can be called whenever needed later, in case something changes the underlying data from which the combo pulls, and we want to update the rowsource.