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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

should MSaccess be ok for my project?

Status
Not open for further replies.

sup919

Programmer
Jan 10, 2002
31
TH
hi there,
I have a question regarding the program. I am wondering whether access performance is enough for my project. If i want to add the data of total 140 fields in 7 different table ( it's the questionnaire result that needed to store in the database) and also another 40 fields in 4 tables(contain lots of word and description) , how long does it normally take to do so? also what is the maximum no of rows & field that access table can have

many thanks

sun
 
Rows and fields may not be your limiting factor. Access is limited to about 2 GB of total data and can become sluggish with more than 5 users.

If your data will grow quickly you may need to consider something else. Other wise you should be fine.

zemp
 
Access is limited to 1 Gb for a single table and 2 Gb for the database. It is also limited to 255 columns (less the number of indexes) in any one table.

If you do a search in forum701, forum700 or forum181 you should get several hits on building questionaire databases.
 
First, you don't want to have a separate field or column for each question. It will cause you lots of problems when it comes to running reports or running queries.

Some hints...build a separate table for questions, with fields like QuestionID, Question, QuestionCategory. Build a Results table with ResultID, QuestionID, Result... This Results table should have few columns and many rows. QuestionID would be a foreign key in Results table.

Following the rules of normalization, you will have more tables with less columns. Normalization really provides a benefit when it comes to running meaningful reports and queries.

Access should be able to handle your situation. Access is more of an issue in the number of concurrent users than the amount of data. While I have had Access implementations of 35 concurrent users, it's advisable to keep it down to 15 or less.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top