append to new table - autonumber field

[Guest]

I have exceed the number of rows I can have in my design of a table. The
first field is an autonumber field that give the user a new job # once the
job info is entered. If I split the tables, what is the best way to join
them for queries. I have tried this before with no success.

 

[Lynn Trapp]

What do you mean you have exceeded the number of rows? There is no maximum
number of rows in an Access database. Do you mean you have exceeded the
maximum file size? If so, there may be any number of causes for that other
than the number of rows.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Guest]

It gives me the error too many fields defined

What do you mean you have exceeded the number of rows? There is no maximum
number of rows in an Access database. Do you mean you have exceeded the
maximum file size? If so, there may be any number of causes for that other
than the number of rows.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Lynn Trapp]

Ah, then you have exceeded the number of columns, not rows. The maximum
number of columns is 256. What that suggests to me is that your table is not
normalized. If you need a table with more than 60 columns (or even fewer
than that) there is definitely some problem with your design. I would say
the first thing to look at is repeating fields. These might appear in a
Persons table where someone is trying to store the names of the person's
children and using fields like Child1, Child2, Child3,...ChildN. You would
break that out into 2 tables like this:

tblPersons
PersonID (PK)
LName
FName,
Address
----other fields specific to a person

tblChildren
ChildID (PK)
PersonID (FK)
ChildName
-----other fields specific to a child

These 2 tables would be related by PersonID. Can you post more information
about your table?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Joseph Meehan]

It gives me the error too many fields defined

That is what I suspected when I read your first message.

You are allowed 256 fields. 99.987% of the time when someone sees this
message it means they have a poorly designed database.

I suspect you have something like

customer name
Orderdate1
Itemordered1
Orderdate2
Itemordered2
etc.

Access is a relational database and it likes to be used that way.

You would have one table with customer information (FirstName LastName
Addressline1 Addressline2 City State Zip etc.

You would have another table with orders with order number, date etc.
and a third table with items ordered so each item is listed by itself
related to an order related to a customer.

This is called normalizing. Not all that hard to do, but the idea does
not come easy.