Table size getting large...

Good morning,

I have a table that currently has about 3500 records, but this number
will be increasing substantially over the next few months to about
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/13606-table-size-getting-large.html
10000+ records. The table holds details for bills of materials for
electronic component assembly. The table has the following fields:

BOMID: The BOM that the detail is associated with
Part Number: The part number for the specific reference locator
Location: The reference locator

The problem is that when one of the products gets revised I have to
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13606
reenter the entire BOM, causing multiple duplicate fields every time
this happens. I was wondering if anybody has an idea that I could use
to make sure this table does not explode in size simply due to
revisions and duplicated data.

TIA

Tim

 
Do share your immediate thoughts or reactions on this issue? We value your views! Login Now! or Sign Up Today! to share your views with us.. Gurfateh!

Tim,

I would focus on business needs first, rather than worry about the table
size. If that's the way it works best for you then leave it as is, the
table size you are looking at is no big deal!
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13606
Just for comparison, I have over two hundred thousand rows in an invoice
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13606
headers table, with close on a million rows in the related line items
table; it's a shared back end on a network with about a dozen concurrent
users, and it works just fine. Contrary to common misconceptions, Access
is not a toy! It can handle large quantities of data (up to 2GB file
size) as long as the overall design is good.

HTH,
Nikos