Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

How do I open access database with no lock?

Discussion in 'Information Technology' started by Andrew `Taersious` Coppock, Nov 3, 2005.

  1. Andrew `Taersious` Coppock

    Andrew `Taersious` Coppock
    Expand Collapse
    Guest

    I am developing an Access database for use over the internet. When I try to
    open the database locally, on the server, it locks out the internet account
    totally, and causes a script error that says, "Error Type: Microsoft JET
    Database Engine (0x80004005) Could not use ''; file already in use." When I
    close Access and refresh the web page, the error goes away. I have already
    set the default open mode to Shared, the default record locking to edited
    record, but that does not help. Am I not going to be able to do this with
    Access 2002?
     
  2. Loading...


  3. Ron Hinds

    Ron Hinds
    Expand Collapse
    Guest

    "Andrew `Taersious` Coppock" <Andrew `Taersious`
    Coppock@discussions.microsoft.com> wrote in message
    news:88B4450D-28F1-4727-A4A1-4E95FC811D68@microsoft.com...
    > I am developing an Access database for use over the internet. When I try

    to
    > open the database locally, on the server, it locks out the internet

    account
    > totally, and causes a script error that says, "Error Type: Microsoft JET
    > Database Engine (0x80004005) Could not use ''; file already in use." When

    I
    > close Access and refresh the web page, the error goes away. I have

    already
    > set the default open mode to Shared, the default record locking to edited
    > record, but that does not help. Am I not going to be able to do this with
    > Access 2002?


    I think the problem has to do with the permissions in the folder where your
    Access database is stored. Specifically, the account that the webserver runs
    under (usually IUSR_ServerName for IIS) needs to have full permissions in
    that folder. What's happening is the webserver is unable to create/modify
    the record locking (.LDB) file for the database. I'm guessing that if two
    users of your website were in there simultaneously one of them would have
    the same error.
     

Share This Page