Well, it's not my problem, but if I had to deal with it I would change the data model to account for the fact that some places are not countries and not provinces or states.

>If you click on Reports button / Members Repartition / United States
>
>then you'll see that District of Columbia and Virgin Islands are already put as State in that model.
>
>What database model do you suggest here?
>
>>>>I don't know what you mean by 'exact.' It's status has not changed. People born in Puerto Rico are U.S. citizens, but it is not a state. That has been the case since 1917. It is a self-governing commonwealth of the U.S.
>>>>
>>>>Here is a summary if it helps (an explanation of commonwealth and territories as at the bottom):
>>>>
>>>>http://welcome.topuertorico.org/government.shtml
>>>>
>>>>The first link above mentions the bill that passed a house committee recently, but it didn't change it's status and even if that bill passes the house or senate, Puerto Rico's status won't change unless/until it's citizens vote on it.
>>>
>>>My main concern is to know if I should keep my country table as is, which includes Puerto Rico or delete that record and add a new record in the US states table to add Puerto Rico. As far as I know, and based from what you said, Puerto Rico is still a country thus no change would apply.
>>
>>It's really neither. It's not a country and it's not a state. It does not fit into your model of countries and provinces/states. I guess it's closer to a state but you wouldn't want to do a SQL Select and come up with 51 U.S. states, would you? (Not to mention Washington, DC, which also doesn't fit).