By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,677 Members | 1,094 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,677 IT Pros & Developers. It's quick & easy.

Unable to use my aspx web application when the access data file is open !!

P: n/a
Hello,
I simply make some aspx web page to update data in a mdb access
database..But when this database is open (not table, juste the mdb in
access) with MS Access, i have an error with my asp.net application (that
tell that the database is either open)
Is there a way to make no-exclusive connection to this database ??

Thanks a lot !!!

Oct 9 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
That is one of the disadvantages of using Access rather than SQL Server, to
the best of my knowledge there is no way to avoid it. However, just out of
curiosity, why do you need to have the mdb open if you are using an ASPX
page to do the updating?
--
Nathan Sokalski
nj********@hotmail.com
http://www.nathansokalski.com/

"user" <us**@user.comwrote in message
news:46**********************************@microsof t.com...
Hello,
I simply make some aspx web page to update data in a mdb access
database..But when this database is open (not table, juste the mdb in
access) with MS Access, i have an error with my asp.net application (that
tell that the database is either open)
Is there a way to make no-exclusive connection to this database ??

Thanks a lot !!!

Oct 9 '08 #2

P: n/a
"user" <us**@user.comwrote in message
news:46**********************************@microsof t.com...
But when this database is open (not table, just the mdb in Access) with MS
Access
OK, step back here...

If you have an mdb file, then what you have is a Jet database - at this
level, this has nothing whatsoever to do with MS Access.

MS Access is a desktop database application development tool which, until
the most recent version, just happened to use the Jet (.mdb) database as its
default database file format...

When an ASP.NET app uses a Jet database, MS Access is not involved at all -
after all, you don't install Access on the webserver...

When you use ASP.NET with a Jet database (a very bad idea, for a whole
variety of reasons), your web app should make a connection to it when
required, and then close that connection as soon as possible. This is true
for any back-end RDBMS, but especially so for file-based databases like
Jet...

What connection string are you using? It should look something like this:
http://www.connectionstrings.com/?carrier=access

And, above all, make absolutely sure that no-one is using MS Access with an
open connection to the Jet database...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Oct 9 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.