Add a Table

[Matt]

The spreadsheet had only one row for each Job#, and about 30 columns. No
biggie. I want all of the information in the second table (I'm really just
adding a bunch more columns) to be related to the first via the Job#. The
entries with blank Job#'s could just be filled in with a random number now,
because they are reference only at this point. I normally do all searches
based on an address anyways, but the Job# is the logical (to me) reference,
because we never repeat them, but sometimes have add ons to it. Should I
just add all the info I want to the first table? Is there a point where the
size of a single table will effect the speed of the database? That's all I'm
trying to avoid, so if I just need to add everything in one huge table, I
guess I could. Thanks for the help!

 

[Matt]

For whatever reason, the meat of this posting has been deleted. For anyone
who is searching past references, John instructed me to create an append
query that worked very nicely.
--
"The only thing worse than an employee that just quits and leaves, is an
employee that quits and doesn''t leave."

The spreadsheet had only one row for each Job#, and about 30 columns. No
biggie. I want all of the information in the second table (I'm really just
adding a bunch more columns) to be related to the first via the Job#. The
entries with blank Job#'s could just be filled in with a random number now,
because they are reference only at this point. I normally do all searches
based on an address anyways, but the Job# is the logical (to me) reference,
because we never repeat them, but sometimes have add ons to it. Should I
just add all the info I want to the first table? Is there a point where the
size of a single table will effect the speed of the database? That's all I'm
trying to avoid, so if I just need to add everything in one huge table, I
guess I could. Thanks for the help!