I don't know of any built-in limitation, but that doesn't mean there's no practical limitation. Why do you need that many fields in your table? Can you explain the structure of your data?
Sounds like your data is not structured "correctly" in a normalized table. I would suggest something like having one buildings table that keeps information in each building, then having a meter reading table that just keeps meter readings. So the data would look something like this:
Building table
BuildingID
Address
Readings table
BuildingID
Date
Reading
Some sample data might be this: Building table
1 1313 Penny Lane
2 456 Pound Drive