>I have three old tables, originally developed in different places at different times, which are going to be linked, since they share about three fields. However, apart from those three fields, the other information they contain will probably not be shared much, if at all. One of the tables has several dozen fields and a large child table, one has many more records and a different child table, and the third is small. Given that they will still be used separately, would it be better to keep them as separate tables and relate them one to one, or is it more efficient to put it all in one table? Either way, I suppose I will be selecting the same fields I need to make different views, whether the fields are in one table or three. Reports of data from the two smaller tables will use the two fields from the biggest table, but reports of data from the biggest table will not need any data from the two smaller tables.

Hi Bret,
My suggestion is one of two things. If you are going to use views in your App then putting everything into one table is fine as long as you structure your views properly. If you are using cursors in your App then leave them separate and pull in each tables data as needed.