You can have up to 255 fields in a table. Keeping all the fields in a single table will make it faster if this table is mostly used for query (few updates). But what if you have a new entities? Or a new set? It will require that you modify the structure of the table and possibly the code. It will be far more easier to update a normalise table in that scenario.

The size of the table may also be a problem if there are many records and/or the size for each record is big.

HTH

>I am building an additional table (.DBF) for my VFP8 application. I'm trying to normalize, de-normalize to maxium efficiency. If this data does not need to be split up (normalized) between 2 or more tables, I'd prefer keeping it in one table. I'll have at least 78 fields (13 distinct entities times a multiple; eg. 6 sets = 13 * 6; 7 sets = 13 * 7, etc.)