Hi, Alex,
Here's my $.02 US -- You can separate the two company values completely by using the sis.dbf with 'Again' --

USE sis.dbf again alias ComboSis

and setting your combo values to the ComboSis table. This way the record pointer on SIS never moves from the record stored in oSis, and as the user moves around in ComboSis you can save/revert/etc. without changing oSis at all.

HTH
Barbara

>Hi,
>
>I have a company table (sis.dbf) that had one row SCATTER NAME'd to an object oSis. Now the user is given the opportunity to select another company from a list in a form. The list comes from the same table. The question is, to what should I set the properties of the list: ControlSource, ColumnCount, ColumnWidths, FirstElement, RowSource, RowSourceType, etc.
>
>In order to allow the user the opportunity to change his mind and back out it seems that the ControlSource should be a properly initialized memory variable or property of the form, and not a property of the oSis object. What do you all think.
>
>TIA,
>
>Alex