I am in the midst of developing a data base that will be updated every month form data from an ASP. The info will be archived at the end of each year to make room for the new year's info.
My concern is: how robust is 2000? I heard that you can have 1Gig in Access 97 (that's what I am currently using), but in 2000 you can have 2 gig.
This has the potential of having about 10,000 records in one table-15 fields, and up to 40,000-12 fields in another and them numerous others as the data base progresses.
I know 2 gigs is a lot, but I want to nip any problems I may have with scalability now as opposed to later. I have SQL 97 (which I am now learning, and have thought about putting the info there and linking it into Access), I am fairly new to SQL so feel a little uncomfortable doing that.
My questions is: For those of you on 2000 what is the biggest DB you are running on it right now (in terms of records and fields)
Thanks

My concern is: how robust is 2000? I heard that you can have 1Gig in Access 97 (that's what I am currently using), but in 2000 you can have 2 gig.
This has the potential of having about 10,000 records in one table-15 fields, and up to 40,000-12 fields in another and them numerous others as the data base progresses.
I know 2 gigs is a lot, but I want to nip any problems I may have with scalability now as opposed to later. I have SQL 97 (which I am now learning, and have thought about putting the info there and linking it into Access), I am fairly new to SQL so feel a little uncomfortable doing that.
My questions is: For those of you on 2000 what is the biggest DB you are running on it right now (in terms of records and fields)
Thanks