I'll give it another try. I have been hosed enough times (most likely by my own mistakes) where I just quit integers in lookup tables.

>I use integer FKs with cbos all the time. The cbo does it's own select cDescr, iID to an array property to grab the records for it's "class". The cbo is BoundTo =.t. and BoundColumn = the key column of the array. It really doesn't matter to me whether those FKs are sequential or have gaps which they usually do.
>
>>The only time I use character PKs is for lookup tables -- this is done because of the bad behaviour of comboboxes. If I were to delete a record in the middle of the table (i.e., a PK is now skipped), numeric or integer fields screw-up cbox behaviour, where character keys do not.
>>
>>So, in my data tables, the FK are also character to match the PK in the lookup table.