How reliable the ASP with MsAccess mdb with 50000 Records.

What do you suggest.

__________________
Gokulan E

I currently have an application that has 120,000 records in one table(Access 2000). May I say, it's running as sweet as the abs on the girl who won the 400m hurdles in Athens this morning.

I guess if we dont try and max it we will ever know. I even found out today Access can run stored procs. Just when you thnk you know...

Wind is your friend
Matt

Great !!!

As long as the performance is not bad. We can work with.....

THANKS WIND

The type of DB used is relative to performance however smart coding and smart queries is where you save the resources. Why I believe the web pages talking to the DB described above goes well is:
connect, get recordset(s), use recordSetName.getRows(makes array(s)!!), close connection and then use the array(s) to render your page copy.

Wind is your friend
Matt

BTW: If a client owns a license for SQLServer I would strongly advise against Access purely for scalability. If the dataset is likely to grow immeasurably, it will fall over eventually.

You can buy a one tonne truck. If you 'ever' think you may need to carry more than one tonne, why bother with the one tonner - go for the big boy to start with.


Wind is your friend
Matt

Hi Matt,

Sure for the long run & data security we will surely consider the above of looking for Data server like SQL/Oracle.

Thanks Wind

I suspect MS Access 2000 is thread safe. I remember, I have seen some such comment in this forum some days back. Could anybody please clarify this ?

Reference from:
http://support.microsoft.com/default...b;en-us;299973

"When you run Microsoft Jet in an IIS environment, it is recommended that you use the native Jet OLE DB Provider in place of the Microsoft Access ODBC driver. The Microsoft Access ODBC driver (Jet ODBC driver) can have stability issues due to the version of Visual Basic for Applications that is invoked because the version is not thread safe. As a result, when multiple concurrent users make requests of a Microsoft Access database, unpredictable results may occur. The native Jet OLE DB Provider includes fixes and enhancements for stability, performance, and thread pooling (including calling a thread-safe version of Visual Basic for Applications)"

Wind is your friend
Matt

I just made a correction to the post 'Posted - 08/26/2004 : 4:55:39 PM' I meant to say scalability not saleability - A very big difference and perhaps the most important word in the post

Wind is your friend
Matt

Mat you said that Access can run stored procedures as wel can you tell me that how we can create and run Stored Procedues on the MS Access ?


(*_*)



Numan
--------------------------------------------------
Love is the most precious thing of this world. So find and grab it!