Handling Large amount of records each day

[florida41]

I want to create a Database that will have about 20 fields such as "Name", "Address","City" etc.. in one table. About 200 records will be added each work day (not on the weekends) using a Cold Fusion web interface. Can Access 2000 handle this amount or should I use a larger Database like Oracle??

 

[BNPMike]

A cuckoo clock could cope with that amount of data.

The beauty of Jet is Access. It's a very good database but there are others even better. If you're not using Access why not use eg MySQL?

 

[willir]

...Meaning yes. (Michael works with H U G E sets of data which makes us mere mortals look pretty whimpy)

Look at max sizes for Access. Your 200 transactions works out to about 50,000 a year. I have a link on my "real work" PC which will send you later.

The question is how long - how many years of data are you going to store?

Richard

 

[florida41]

I think this database will be around for around 5 years.

So I assume from what you are both saying I am okay using Access 2000 Database for this project?

 

[BNPMike]

I'd put money on Jet handling that every second. Not that I've any evidence whatsoever for doing so...

Sorry to disappoint you willir. I did have about 400 million records in a table once (DB2) but currently I'm down to about 500 records in MS SQL Server and about 100 in Access. So I'm currently in the market for a reasonably priced cuckoo clock in a tasteful colour.