More specific question concerning Access 2000 limitations

[Gary1984]

Hi guys,

I'm developing a database (a student tracking system actually) of which one table (with exam results of students) has to hold over 100,000 records in the future (this table consists of 7 fields of which 3 are lookup-fields). Is this physically possible and if so, how do you guys think it will affect the performance of the database?

tblResults

resultID (PK)
studentID (FK)
taskID (FK)
grade ' 0,0 - 10,0
absence ' in hours
week ' week number 1-52
semester ' semester 1-4
classID (FK) ' school class
notes ' string length not more than 20

And is there a way to auto-compact the database after closing it?

Any advise on this subject is more than welcome.

Have a nice weekend!

Gary (Lange36"AT"imt "DOT"hva"DOT"nl )

[NeoPa]

Hi guys,

I'm developing a database (a student tracking system actually) of which one table (with exam results of students) has to hold over 100,000 records in the future (this table consists of 7 fields of which 3 are lookup-fields). Is this physically possible and if so, how do you guys think it will affect the performance of the database?

tblResults

resultID (PK)
studentID (FK)
taskID (FK)
grade ' 0,0 - 10,0
absence ' in hours
week ' week number 1-52
semester ' semester 1-4
classID (FK) ' school class
notes ' string length not more than 20

And is there a way to auto-compact the database after closing it?

Any advise on this subject is more than welcome.

Have a nice weekend!

Gary (Lange36"AT"imt "DOT"hva"DOT"nl )

I don't imagine you'll have too many problems with the volumes involved Gary.
Other experts are more familiar with Access size limits (No database can exceed 2GB in size), but I would expect the performance to be quite acceptable. This is, of course, heavily coloured by your initial expectations.

There is an option in Access 2K and beyond, where you can set a database to Compact & Repair automatically on closing the application (Access).

[ADezii]

Hi guys,

I'm developing a database (a student tracking system actually) of which one table (with exam results of students) has to hold over 100,000 records in the future (this table consists of 7 fields of which 3 are lookup-fields). Is this physically possible and if so, how do you guys think it will affect the performance of the database?

tblResults

resultID (PK)
studentID (FK)
taskID (FK)
grade ' 0,0 - 10,0
absence ' in hours
week ' week number 1-52
semester ' semester 1-4
classID (FK) ' school class
notes ' string length not more than 20

And is there a way to auto-compact the database after closing it?

Any advise on this subject is more than welcome.

Have a nice weekend!

Gary (Lange36"AT"imt "DOT"hva"DOT"nl )

Select Help from the Microsoft Access Menu Bar and do a
Search for: Access Specifications. I have a feeling that a majority of your
questions will be answered there.

[PEB]

And the performance of your database depends on you :)

You can have a database that crashes at 10000 records and database that handle millions...

If you use not appropriate queries, functions... certenly the increased volume should be processed slowly!

Take care about the queries that you do! there is some rules that should be respected and everything will be all right! If you look for them those rules are mentioned in this forum multi times...

Take care man!