Access 2003

  • Thread starter Thread starter Ann
  • Start date Start date
A

Ann

I have been assigned a project to create a very large db.
in access. It has 52 columns and is giving me error
messages already that I have exceeded the # of columns
allowed in a table. I can't find an answer on the number
of columns allowed in a table anywhere.
Personally I think this is way to big for Access. It is
going to be a problem.
What are your thoughts. Help!
 
Ann said:
I have been assigned a project to create a very large db.
in access. It has 52 columns and is giving me error
messages already that I have exceeded the # of columns
allowed in a table. I can't find an answer on the number
of columns allowed in a table anywhere.
Personally I think this is way to big for Access. It is
going to be a problem.
What are your thoughts. Help!
Click to expand...

The column limit is 255, but you also have a limit for the total bytes per
row. You are probably hitting that ceiling.
 
I have been assigned a project to create a very large db.
in access. It has 52 columns and is giving me error
messages already that I have exceeded the # of columns
allowed in a table. I can't find an answer on the number
of columns allowed in a table anywhere. \
Click to expand...

Try looking for "Specifications" in the online help. You are limited
to an (absurdly large) 255 fields; but every time you change the
design of a field in table design view, it uses up a slot. You can
recover the full 255 by using Tools... Database Utilities... Compact
and Repair Database.
Personally I think this is way to big for Access. It is
going to be a problem.
What are your thoughts. Help!
Click to expand...

One thought is that a 54-field table is VERY wide for *any* relational
database, and that you should carefully consider whether it needs to
be split into two or more tables in one-to-many relationships. Does
the Entity modeled by this table really have 54 non-repeating, atomic,
independent attributes?
 
Hello Ann,

Are you trying to do 52 columns (fields) in one table (i.e. tblCustomerInfo
with 52 fields)?
if this is the case you have to break your fields in different tables which
its always a better practice (Normalization).
Hopes this helps.
 
Back
Top