<< I just experienced the kind of goofiness you indicate in lookup settings. I believe it was due to my altering a column name after adding it to a table. In other words, adding the column to the table saves without looking in forms but altering the column name runs some internal update routine while saving which may be responsible for this behavior.
>> I saw this a couple of months ago. I did some kind of table restructuring (adding a column or renaming, or redefining) and the result was that the controlling table on a bunch of db lookup combo boxes in forms got changed. -- Larry
