Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LOOKING FOR DATABASE SAVVY 2

Status
Not open for further replies.

TNN

Programmer
Sep 13, 2000
417
US
Using an Access Database I am planning a table with approx 155 fields which would have to hold approx 104,000 records.

Can anyone tell me what problems I might run into with such a large number of records???
I'll be creating recordsets using SQL by way of ADO. What kind of a response time will I have when creating recordsets and inserting or updating data??

TNN, TOM
TNPAYROLL@AOL.COM

TOM
 
the number of records is not a problem. If the 155 fields are in a single table, there is a large potential for problems. Ms. Access has a limit of 255 fields in a recordset. Since a single self join would exceed this limit, I would anticipate some issues with the schema. You should be aware that Ms. Access counts things as fields in recordsets which are not - stricyly speaking - FIELDS of the results set.

If this were within my purview, I would almost certainly try to break up the table of 155 fields into three or more subsets and use relationships and joins to aggregate the fields only as necessary for a specific task.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over
 
Tom,

I agree with Michael, totally. You might want to think about breaking up your table into tables based on fields that would appear on one form together. That approach has helped me in the past.

If you want to post some detail on the data, we might be able to give you more specific help. Kathryn


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top