Dear Peter
thanks for the help
I found a couple of places where I was not specifically closing an
OleDbDataReader and having fixed them it now seems very stable
A word in defence of Access
In our situation where most of the system is being used in house the design
features of Access (Forms, Reports, VBA) are a delight to use. We would not
have more than 5 people on at any time.
To provide a reasonable degree of public visibility the same database works
very well in ASP and ASP.NET so long as the connection times are as low as
possible.
To test the stability I opened 100 almost simultaneous connections to the
server and each one performed perfectly and pretty quickly too.
Every time I mention Access on these newsgroups people seem to hold up a
cross and predict all manner of problems. But the reality is that for the
right site and the right application Access is superb.
Once again thanks for the help you gave - it allowed me to fix the problem
All the best
Phil
"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:EE**********************************@microsof t.com...
Phil,
The best thing you can do for yourself is get rid of Access and switch to
say, SQLExpress. Since you indicated that for some reason you cannot do
this,
the next step would be to make absolutely sure that all connections are
properly and promptly closed immediately after the unit of work using the
connection is complete. Access just was never designed to be a multiuser
database.
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"phil" wrote:
>We have a small website using Visual basic and ASP.NET. We hold a
database
in Access format which is opened with the following 3 lines
Dim m_dataBase As String = "Provider=Microsoft.Jet.OLEDB.4.0; Data
Source=C:\callidusWorld\app_data\webAccess.mdb"
Dim myConn As New OleDbConnection(m_dataBase)
myConn.Open()
most of the time this works as expected but every now and then it seems
unable to open the database and throws an exception.
Any subsequent call continues to raises the same exception and the only
remedy so far is to reboot the server which is far from elegent.
I cannot change to another database and never had this problem with ASP -
if
any one has any ideas I would be very grateful.
Many thanks in advance
Phil
The rather unhelpful message from ASP.NET is that it's an unspecified
error
Unspecified error
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Data.OleDb.OleDbException: Unspecified error
