Results 1 to 10 of 10
  1. #1
    Join Date
    Nov 2008
    Posts
    12

    Unanswered: Simple Data Base, I want to Share it on my Network... NEED HELP!

    I have a very simple Data dase that I want to be able to share on my it on network. I have it on a Mapped Net work Drive. When I open the Database from 1 Computer it Creats a Small file in that Directory that shows a Lock. When I go to open it from a different computer it Doesnt do anything at all. No errors, nothing. I've looked 100's of posts on this topic, and I cant find the answer. This should be pretty simple what I'm trying to do.

    Thanks for your help!

  2. #2
    Join Date
    May 2005
    Location
    Nevada, USA
    Posts
    2,888
    Provided Answers: 6
    Paul

  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    ▲ Ageed. Not splitting shouldn't cause that error though... should it?

    It should be simple yes. But there are so many things that could be wrong... and I don't know where to start.

    Can you open it from a different computer FIRST? Does it only work on one computer regardless? Might be a references problem, could be a shortcut problem...
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Nov 2008
    Posts
    12
    Quote Originally Posted by StarTrekker View Post
    ▲ Ageed. Not splitting shouldn't cause that error though... should it?

    It should be simple yes. But there are so many things that could be wrong... and I don't know where to start.

    Can you open it from a different computer FIRST? Does it only work on one computer regardless? Might be a references problem, could be a shortcut problem...
    Will open from any of the computers. But will not allow it to be open at the same time. If either computer has it open, the other computer can not open it.

  5. #5
    Join Date
    May 2005
    Location
    Nevada, USA
    Posts
    2,888
    Provided Answers: 6
    I've not run an un-split application, so not sure what could cause the problem. My first thought was that the setting in Tools/Options/Advanced for the open mode is set to Exclusive. In any case, it should be split and the problem may go away anyway.
    Paul

  6. #6
    Join Date
    Nov 2008
    Posts
    12
    Quote Originally Posted by pbaldy View Post
    I've not run an un-split application, so not sure what could cause the problem. My first thought was that the setting in Tools/Options/Advanced for the open mode is set to Exclusive. In any case, it should be split and the problem may go away anyway.
    How do I even go about slpitting it? I guess I would have to read into this....

    -Dave

  7. #7
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Tools - Database Utilities - Database Splitter might be a good place to start?!

    Check that option too... if the open mode is set to Exclusive, this would explain it.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  8. #8
    Join Date
    Apr 2004
    Location
    Kingsland, Georgia
    Posts
    231
    hey...I'm on board with the splitting, too. But to answer your original question, the way to allow multiple users to access the one mdb on the network is to have them use a shortcut that open access first, then the database, as opposed to them going straight to the file and double-clicking it to open. This has been happening on our network, too, and just started within the last 3 months, I believe. Could be a security patch or something, I don't know. Anyways, have the users use a shortcut with target string something like this:
    "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "J:\Common\TEST Weld Db\Weld.mdb"

    Of course, splitting the tables from the rest is a great idea, too.

  9. #9
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Quote Originally Posted by jmahaffie View Post
    hey...I'm on board with the splitting, too. But to answer your original question, the way to allow multiple users to access the one mdb on the network is to have them use a shortcut that open access first, then the database, as opposed to them going straight to the file and double-clicking it to open. This has been happening on our network, too, and just started within the last 3 months, I believe. Could be a security patch or something, I don't know. Anyways, have the users use a shortcut with target string something like this:
    "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "J:\Common\TEST Weld Db\Weld.mdb"

    Of course, splitting the tables from the rest is a great idea, too.
    NO. Use the vb script in the 2nd page of the code bank (of course, only use on a splitted mdb file) if you want TRUE multi-user capability. Guarantee this will work! Otherwise, plan on "Locked by another user" type errors. Once a single user locks the shared *.ldb file, you'll know you need to use the vb script.

    It's the multiple users in the same *.LDB file that you have to worry about. Many users opening an *.mdb on a network and one of the user's eventually locking their workstation/losing network will cause the corruption of the shared *.ldb file and the error "Locked by another user" preventing OTHER users from opening the same mdb file.

    If you have shortcuts scattered and all users are STILL opening the SAME mdb file, then you STILL have the same problem (it doesn't matter! - eventually one of them will lock the shared *.ldb file!! - Guaranteed!) You need to have a script that puts each user in their own mdb file (and based/cloned off a single source mdb file when the script is launched.)

    It's your choice though...either you can deal with the "locked by another user" errors as they come up (and hunt down all the users to have them close out of the mdb so you can compact/repair/fix the *.ldb), OR you can simply use the script. Most likely, it depends on how often your users lose connection to the mdb file and lock the *.ldb file (and you get the "locked by another user error.). I just don't want you to think that creating separate shortcuts for all users alleviates this problem - it doesn't!

    Note that the *.ldb file will ALWAYS show a lock when someone has the mdb file open (it's MS's method for controlling the users in that mdb file.) The *.ldb file will disappear when all users have exited the mdb file. It's when other users start getting "Locked by another user" errors or "hanging" *.ldb files when trying to open the mdb file that you get concerned.
    Last edited by pkstormy; 10-31-09 at 02:03.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  10. #10
    Join Date
    Oct 2009
    Posts
    4
    1. Split database, as many have suggested. It is always a good idea to split a database as it helps in maintaining the forms, reports, etc. When you split the databse, it will create what is known as a front-end and a back end. The back-end is where the actual data resides in tables. The front-end is where everything but the data resides.

    2. Have the front-end loaded on every computer that your want to use the data.

    3. Users open their front-end. Write a VBA function that will LINK (turn to MS-Access help to see how this is done automatically in VBA code) the database tables to the front-end. The user then uses the database as if the data resided on their own computer. The Access backend database table will lock a record someone is working on but not the entire table so other people can work on other records.

    NOTE: Using a BIG database with very LARGE queries may adversly affect performance. I have had more than 15 persons located at various locations (that is, various cities) be able to access a shared database in this manner. No one reported any problems. Of course, you must have a very good network for this to function almost flawlessly.

    I hope this helps!

    Amin
    Last edited by Amin Bardai; 11-02-09 at 13:17.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •