Multiuser Environment(Urgent Please!!)

[Sameer]

I have developed form using Front page(webbot components) and sending the data to MS Access.The form is in .asp format.There is approx.250 user who will be filling this form on our companies intranet based on customer calls they receive.There are around 25 fields in the form and approx.8000 forms will be filled everyday.
I am planning to generate reports based on nature of calls for various levels of management on regular basis.
Can anybody suggest, if I am moving in the right direction by using MS Access as send result option thru webbot or it is not good for this kind of big user numbers and data size.What is the alternate suggestion to use to make it a robust solution.
I will appreciate urgent response to this and any kind of suggesstions are welcome.
To make it clear, I am not a core tech guy and this I found to be easiest solution for me to develop and use.
Looking forward for very urgent feedback and suggestion.

 

[Sameer]

It is urgent.Any help or clue is much appreciated.

 

[Pat Hartman]

Your urgency has nothing to do with when people will answer your question. We are all busy people with deadlines. The people who answer your questions don't get paid for their help and they can't help unless they have found the time to read questions in the forum.

8000 transactions a day should not be too much for Access to handle. The problem will be how much data you need to accumulate before you can start purging. If you operate 7 days a week, that's 56,000 a week and 240,000 a month. It won't take long before your row count is in the millions. Access isn't going to choke at some fixed number of rows but it is limited to 2G for a database so your column sizes would directly influence the number of rows a table could store. If you have multiple tables, you can store them in individual databases so the limit actually translates to 2G for a single table.

Large scale databases such as DB2 and Oracle can support huge tables. I've used DB2 tables with 100,000,000 rows (telephone company records). SQL server is much more limited.

 

[Sameer]

Thanks for your help.I do understand the busy schedules everybody has but it was just a request...and bring it back to attention...I didn't expect it to come back like this.And I understand these forums and also that no one gets paid to share the knowledge...and thats what it is for.
Anyways, I appreciate your help.