Hi Sylvain,

Thanks for responding. The BoundTo property is not set to .T. but when reading the help on this, it says that "This setting provides compatibility with Microsoft Visual FoxPro 3.0 and 2.x versions of FoxPro." and it seems that it is unnecessary.

Here are the settings of a couple of other fields (not that I will not try the above but would like to understand this better):

- RowSource is set to a view, field name ie. "Queues.QueueName"
- RowSource Type is set to: "6 - Fields"

- my understanding is that these setting will build the list contents from the specified field

- note that the view contains two fields with the first one being "Queue_ID" and the second one being "QueueName".

- BoundColumn is set to the default of 1 but the help says that this only has to be set if there are multiple columns in the list and we are binding to something other than the first column.

But maybe we have to do a few more things that "supposed to" suggests - this would be based more on experience ie. maybe we have to set BoundTo to .T. even though the help files says this is for backwards compatibility with VFP 3.

Albert



>One thing I would check is to make sure the BoundTo property is .T.

>>But every now and then when the user fires the form, the picklist face is empty (ie. like row zero). When the picklist is then chosen by the user, all the rows are there (so the combo was built properly it seems). Also, if I have the user call me, I can check their users.dbf record across the network at that moment and the bound field does indeed still hold the correct data.