>Hi,
>
>What is the best pratice, 3 or 4 small tables in order to split the data or only 1 table but with a lot of fields (350).
If you need a single table with 350 fields, this would often - but not always - indicate a problem with normalization. First of all, try to follow the normalization rules. Do you still end up with a single table with 350 fields?
For instance, you should not have repeated data in separate fields, but in separate records (in a separate table). In one proposal for a system that recorded grades for university students, I saw seven fields for the subjects, and seven more for the corresponding grades (one record per student). This was clearly not normalized, and continuing with this implementation would have caused lots of problems.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
