Query/ASP page problem

[mobutu_fariahe]

First, let me just say that I am a novice when it comes to ASP pages and db connectivity! This may be more of an ASP issue but I thought I'd also post it here...

Here's the problem. We created an export tracking database in Access. We've automated reporting from the db to a web page via an ASP page. The ASP page hits a query, which then gets represented on the returning ASP page as a table. Pretty simple!

The report works great so long as no one is using the Access db. Once someone is in the Access db, when you access the report page, it returns a server error (500) and no page.

Here's the simple code on the ASP page:

<%
' FileName="Connection_ado_conn_string.htm"
' Type="ADO"
' DesigntimeType="ADO"
' HTTP="true"
' Catalog=""
' Schema=""
Dim MM_ExportsTracking_STRING
MM_ExportsTracking_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\Logistics\Database\ExportManagementSystem.mdb; Persist Security Info=False"
%>

Any idea what could be causing this? I assumed that Access would allow concurrent users to use the db...

I looked briefly at the security settings. Assuming the db was unsecured when not open, would this allow open access when the db was not in use? If so, why would an unsecured db then prevent someone from accessing a query?

Any help is deeply appreciated!

Thanks!

 

[FoFa]

Will the DB allow multi-users in using Access (not ASP)?
If you are designing in the DB it will put it in exclusive use mode also and not allow access.

 

[mobutu_fariahe]

I thought that the db would allow multi-user, but I'll check.

How can I change it to non exclusive (and enable multi user)?

Sounds like this might be the solution to my problem.

THANKS!

 

[mobutu_fariahe]

Lots of time invested in my problem but so far no solution.. I've set the database to shared, no record locking. There's no security set.

The db can be used multi user in Access. Still, when one or more users are in the db, the asp fails to execute and return a report table.

This has to somehow be related to either record locking in Access or the cursortype or locktype ASP statements conflicting w/ the db.

Most frustrating.

Here's examples of the ASP code related to the recordset:

et rsTracking = Server.CreateObject("ADODB.Recordset")
rsTracking.ActiveConnection = MM_ExportsTracking_backend_STRING
rsTracking.Source = "SELECT * FROM qryTrackingSheetWebSource"
rsTracking.CursorType = 0
rsTracking.CursorLocation = 2
rsTracking.LockType = 1
rsTracking.Open()

rsTracking_numRows = 0
%>
<%
Dim Repeat1__numRows
Dim Repeat1__index

Any ideas?

Thanks!!

 

[FoFa]

Typically I just let everything but the SQL and CONNECTION default and life is good. And this only happens when another use is in the DB correct? The other users MSAccess system is also NOT set to exclusive use right? If someone is using ACCESS to run the system, each workstation has to be verified to not exculsive, but that is usually the default or Access will not share amoungst itself also.

 

[mobutu_fariahe]

Thanks man.. great suggestion.. double checked the database on the user side, no luck. open/exclusive has not been checked for any user or group...

Same result...

Any other ideas?