Answering another problem you may run into, you are using a lot of data types that may or may not be kinda.. big.. for what they hold.

sex is usually a boolean of sorts, evena bit, or a charachter, but certainly not a float. Unless you are counting half instances and large ones, since you are using a float of 12 digits or 3.

I'm assuming ageyears, is supposed to be the age in years. It's usually smarter to use a date-like format and calculate it on the fly. (where age >= 01-01-1980 and age < 01-01-1981 for instance).

A little oversizing isn't bad. But too much and you wind up with a db that takes up a LOT more space than it should. You can also get truncating errors if you think a float(12) sex in cases, would relate properly to float(3) in geo_m_count for instance, if it were a foreign key.