none
Ms Access cannot lock file RRS feed

  • Question

  • Hi,

    I am trying to open an access 2013 database to update it on a local network (2 computers in Homegroup). The database is on computer A, the application is on computer B.  The remote application is in Vb.net and uses  the connection string

    Public conAccessString AsString= "Provider=Microsoft.ACE.OLEDB.12.0;Data Source="& filePath & AccessDBName & ";Persist Security Info=False;"

    The database(accdb) file will only open in Read Only mode on computer B as it cannot write or open an laccdb lock file on computer A.  Note computer A runs W10, computer B runs W7.

    I have spent days researching all this and security is set on the folders and file on computer A (networked/shared "W" drive) which holds the database so that the Owner, <My Login Name> and"Guest" have full control, read and write access. The Attributes: Read-only is unset. the drive is "Shared",

    what more do I need to set/unset??? NB this used to work well, I have recently had computer A "cleaned", ie C drive cleared and W10 plus Office 2013 reloaded owing to Hacker activity,; now does not work for application running on Computer B.

    I would appreciate all input!!!

    Bruce Caldwell

    Sunday, April 15, 2018 12:18 AM

All replies

  • Hi Bruce,

    Just wanted to make sure I understand. Did you say the same setup used to work before? I am wondering if you had Access 2010 installed on Computer A before the "clean up" because it may be possible you'll need a 14.0 driver for Access 2013. Either that or I can't exactly remember if OLEDB was removed from 2013, so you may have to use ODBC instead.

    Just my 2 cents...

    Sunday, April 15, 2018 4:45 PM
  • When logged on to computer B (the application's computer) using the same user profile under which the application is running, can you use Windows Explorer to manually create and delete a file in the same folder on computer A that holds the database?

    Dirk Goldgar, MS Access MVP
    Access tips: www.datagnostics.com/tips.html

    Sunday, April 15, 2018 7:10 PM
  • Hi LegacyGT,

    Did you try to close connection and release the database after completing your operation on database from your VB.Net application?

    If not, you can try to do it may solve your issue.

    Regards

    Deepak


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, April 16, 2018 7:45 AM
    Moderator
  • The bottom line is that the user attempting to open the database from your VB app should full control of the "folder" where the Access database is located, not just read/write access to the database file. I would verify your settings again because it sounds like the permissions to the folder have not been set correctly.

    Also, Homegroup was removed in current versions of Windows 10. You may need to walk through a new process in order to provide folder/file sharing:

    https://support.microsoft.com/en-us/help/4092694/windows-10-changes-to-file-sharing-over-a-network

    In addition, in a workgroup environment the users and their passwords should be mirrored on each machine.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Monday, April 16, 2018 12:25 PM
  • Hi LegacyGT,

    Is your issue solved?

    I find that you did not follow up this thread after posting the issue.

    If your issue is solved then I suggest you to post your solution and mark it as an answer.

    If your issue is still exist then try to refer the solution given by the community members.

    If then also you have any further questions then let us know about it.

    We will try to provide further suggestions to solve the issue.

    Thanks for your understanding.

    Regards

    Deepak


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, April 27, 2018 9:52 AM
    Moderator