Tamar,

Have you tried tracing the code to see exactly what's happening in the second call to frmBrowser?

I found the culprit - it was a combobox that is part of frmBrowser - but to me raises more questions. At design time, I have set RowSource to a name of a temp table which was created only in the Init of frmBrowser. So, what I did was leave RowSource blank at design time, and let frmBrowser.Init do the setting. The right thing to do.

Big question now is: how come though frmBrowser works during the first time calls?

Maybe you could shed light on this 'phenomenon'... =(

Dennis