Re: Access97 DB locks up the asp code at times

From: joker (no-spam_at_netzero.com)
Date: 08/09/04


Date: Mon, 09 Aug 2004 08:37:29 -0600

The .ldb file is created when the database is accessed & deleted after
you have finished with the .mdb file.

ziggs wrote:

> Thanks for the quick reply.
>
> Almost all employees are set to read only, so I would assume that one
> of these users created the query off the asp and that's the problem.
> I'm not sure why, but I could never see the employee.ldb on the folder
> so I never could check that. Thus, it most likely is the permissions
> problem with the folder.
>
> From memory, to answer your questions that I neglected to detail out
> (sorry), the error message was:
>
> Error Type: (0x80004005)
> Unspecified error
> employee.asp, line 6
>
> Thus, it was pointing to the line of:
>
> "my_conn.Open ConnString"
>
> that I was referring to but didn't detail out.
>
> I'll chat with our IT group about setting the proper permissions.
> Unfortunately, I haven't had much luck in the past describing what I
> actually need since I'm obviuosly weak in this area.
>
> If you have any specific advise I can pass on, I would appreciate it.
> The four current groups are Administrators, Everyone, Managers, and
> System under the Security tab. Your suggesting to add at least the
> IUSR_MachineName account name.
>
> I guess my main problem is that I'm not positive about the correct
> combination settings to use for the web sharing, sharing and security
> areas. My goal is that everyone can run the asp that accesses the mdb
> but not be able to open or view the folder off any share, Managers can
> open the share and change the mdb and Administrators obviously have
> full control to all.
>
>
>
>
>
> On Sun, 8 Aug 2004 14:05:30 -0400, "Bob Barrows [MVP]"
> <reb01501@NOyahoo.SPAMcom> wrote:
>
>
>>ziggs wrote:
>>
>>>I have an Access 97 DB called employees.mdb within a NT security type
>>>folder. Other users have write privileges to this document to make
>>>updates. This Access DB is only used for an ASP called employee.asp
>>>that's within the same folder. Here's the connection string example:
>>>
>>><%@ Language=VBScript %>
>>><% Dim my_conn, rs
>>>
>>>ConnString = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ="
>>>& Server.MapPath("employees.mdb")
>>
>>Nothing to do with your problem, but you should be using the native Jet
>>OLEDB provider instead of the ODBC driver:
>>
>>ConnString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source="
>>& Server.MapPath("employees.mdb")
>>
>>The ODBC provider has been deprecated.
>>
>>
>>>Set my_conn = Server.CreateObject("ADODB.Connection")
>>>my_conn.Open ConnString
>>>
>>>set rs = server.CreateObject("ADODB.Recordset") %>
>>>
>>>This asp has been working without major problems for about 2 years.
>>>On most occasions, a user can open the Access DB, make changes and
>>>close it without any problems. However, on two occasions, a problem
>>>has occurred after a user opened the Access DB.
>>
>>What problem?
>>
>>
>>>My only guess is that
>>>someone accesses the employee.asp, which queries the Access DB when
>>>the Access DB is opened and being changed. Once this occurs, the
>>>employee.asp delivers an error code and complains about the connection
>>>line of "my_conn.Open ConnString".
>>
>>What error code? What error message? You're asking us to solve your problem
>>blindfolded.
>>
>>
>>If I had to guess, and I do, I would guess that you have a permissions
>>problem. All database users, including the IUSR_MachineName account, need
>>filesystem read/write permissions on the folder containing the database
>>file. Users must be able to create, modify and delete the .ldb locking file
>>in the folder containing the database. It is not enough to grant permissions
>>for the database file.
>>
>>Bob Barrows
>
>



Relevant Pages

  • Re: User access on a company intranet
    ... Yes they need full permissions on the folder where the backend is. ... You wouldn't need to do this in your copy of the database. ... However you can toggle the shiftkey bypass from another mdb file. ... When you want to implement security, you create a new mdw file, ...
    (microsoft.public.access.security)
  • Re: Have database mismatch, can I move NTDS.dit and Exchange to new identical server?
    ... Check the physical location of the Winnt\NTDS\ folder. ... Check the permissions on the \Winnt\NTDS folder. ... as it may not be the database that is the ... MCSA + Exchange ...
    (microsoft.public.win2000.active_directory)
  • Re: Help - locked out of database
    ... IT checked all the permissions and everything seems to be ok. ... "Joan Wild" wrote: ... I have poured a year into this database - is there someway to recover this? ... You need, at minimum, modify permission on the folder. ...
    (microsoft.public.access.security)
  • Re: Is there blog add on for FP2003
    ... tools/ web settings/ database tab. ... browse to the .mdb for the blog and add it. ... you'll have to edit the config file to reflect the new folder name. ... >>Microsoft MVP FrontPage ...
    (microsoft.public.frontpage.addins)
  • Re: security only works on my PC
    ... I checked the permissions box and the Users group has no ... Open/Run and open exclusive on database object ... "Joan Wild" wrote: ... properly on the single mdb. ...
    (microsoft.public.access.security)