I have 150K items in a main table. I need to create another table called "item properties". This will contain information that is specific to the items but that doesn't need to be in the main table.

I made the table and arranged the fields therein and created the relationship. I then exported the main field "model number" and imported it into the new table. Now the ITEM PROPERTIES table has all the same records as the main table. However, when I create a new record in the main table, It does not automatically create one in the ITEM PROPERTIES table. How can I automate that. I am not the only one entering records.

Thank you

Turn on allow creation of related records. With this option on, if you type in data into the properties field, it will create the record automatically.

Also if you have multiple properties to each Item (one to many) then you could use a portal to display and enter in multiple properties.

Perhaps I can clarify. The PROPERTIES table contains the feed contents that will be sent to various websites. These websites have different field names for the same data, so in order to have the field names in my table match, I have to create multiple tables. (unless there is a better way to do it) does this make sense?

Not to me. Perhaps you can give a more concrete example.

Perhaps I can clarify. The PROPERTIES table contains the feed contents that will be sent to various websites. These websites have different field names for the same data, so in order to have the field names in my table match, I have to create multiple tables. (unless there is a better way to do it) does this make sense?

Let me paraphrase back what I understand so far, you have a table of items, each item has an id and some data fields, e.g. field1, field2, field3, etc. You have about 150K items right now.

I'm not really clear what the purpose of the properties table is? If it is just to "map" from your field names to your destination database field names you probably are going about this wrong and want to create a table of field name mappings one record per destination.

Simply creating massive copies of your main items table with slightly different field names and one-to-two extra fields doesn't make sense to me.