What kind of information/data are you trying to add to these tables?
If your tables are designed correctly, you will probably should be adding new records, not new fields.
An example of this that I see a lot is that someone has a table of monthly revenue, so each month they want to add a new field (column) for a particular month's revenue. That is the wrong way to go. Instead of having a field for each month, they should have one field for month name, and one field for month amount. So for a single client, instead of have one record with 12 different month fields, they should have 12 different records.
It may sound counter-intuitive, but designing your database in this manner is actually preferred ("normalized") and makes it more efficient and easier to work with.
For example, what if you had a recipe database, and you had one record for each recipe with 50 different fields for ingredients. Now say that someone comes along and wants to know all the recipes that have chocolate as as ingredient. If you have 50 different ingredient fields, you have to search 50 fields (have fun writing that query!). However, if you only have one ingredient field per record, you only have to search one field.
Do you have a scenario like this going on where you might need to rethink how you are structuring your tables?