Hal

I don't understand your situation well enough to tell you what you might
need yet.

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Hal" wrote in message
...
Jeff, thanks for the reply. Somehow I assumed that I needed to separate
the
"account transaction" data for each utility type since not all of the
data,
e.g. "gallons", kWh, therms, for is the same.
Are you recommending that I use one table to hold all of the transaction
data, and have the database "relate" the individual transaction to the
"building/utiltiy" tables?

--
Thanks, Hal


"Jeff Boyce" wrote:

Hal

Why? As in "why do you believe you need that many tables?" In a
relational
database like Access, you need one table per "entity". What entities
(things about which you wish to keep data) do you have?

One phrase in particular caused me to ask ... "... and individual tables
for
each utility account ... hold monthly transaction data." If I'm not
misinterpreting, this would mean that every single account gets its own
transaction table. That would be a SPREADSHEET, not a relational
database
table.

More info, please...

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Hal" wrote in message
...
I'm trying to construct a database the relates a building info table
with
a
utility accounts table, utility provider table, utility type table, and
individual tables for each utility account the will hold monthly
transaction
data. I've successfully related the building table and the utility
account
table together, and have related the supplier table and utility type
table
as
well. I have not been able to properly connect the individual utility
account
tables to either the "building" table or the "accounts" table.

I get a "too many indexes" error message.
Any help on this issue. Please
--
Thanks, Hal