>I have many uses of combo boxes for users to make selections from a static ("fixed") pick-list (i.e., they are not allowed to add to it). The data source for the pick lists are tables with 2 fields -- the first field will be for storing a unique ID. The second field will be the value/description of their choice that is displayed in the combo box. These tables are always indexed on the unique id, and when needed, the description. When I start up a form a parent table is opened as well as all the needed child pick-list tables for the combo boxes. I set the order to the child tables to their respective IDs and set a relation to the ID from the parent to the child. The parent table stores the child table ID (bound column of the pick list is the ID field from the child table). The problem only exists if I delete a record in the child table (deleted is always set ON). As I scan through the records of the parent table in the form, the child table is displaying the wrong
>value/description. For example, if the value in the parent table is 9, it shows the ninth non-deleted record from the child table, NOT the child record whose ID is 9.
>
>I am using VFP version 3.0b and must do so because not all our users are in Win95 yet. Any advice on correcting this problem?
>
>TIA,
>
>Mark

I have strong feeling that temporary relationships make more harm than help. Is it possible for you not to use them at all and perform SEEK in picklists directly in code? At least you will never get wrong picklist record.