>Borislav
>I found the problem and a solution. I had a relation in the data environment of the calling form that linked to the controlSource of the comboBox on the "called form". Deleting the relationship or setting the dataSession property on the "called" form to "private" remedied the problem.
>
>Question for you: Do you generally set the dataSession property to private on your forms? I do on reports, but have not been doing so on reports
>
>thanks, Vince
Yes, All of my forms (except one or two) are with private Data session. Also I never use a Data Environment in the reports. I prepare the cursor that I want to print before the report and then just run the report based on that cursor. That gives you a possibility to use one report for many different data sets and completely different information. I use ONE report to print all my nomenclatures ( I don't know the exact words for this type of tables on English).
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.