Welcome to SPN

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

Sign Up Now!

Consurrent User Problems

Discussion in 'Information Technology' started by Mark, Jul 28, 2006.

  1. Mark

    Mark
    Expand Collapse
    Guest

    I have created a concurent user Access system with a front end on each
    user's computer and a back end sitting on a common server. I am not
    using the user level security. I have check that the dbf is shared and
    row level record locking is enabled.

    More than one person can enter the system but the moment forms or
    reports are accessed from the Switchboard error messages saying
    somebody else has the table open in exclusive mode.

    How do I keep this from happening?

    Thanks for any help on this issue.
     
  2. Loading...

    Similar Threads Forum Date
    After FIR, Social Media Users Wary of Offensive Jokes on Sardars Information Technology Oct 2, 2013
    USA US govt secretly collecting data on millions of Verizon users: Report Breaking News Jun 6, 2013
    using spiritual name as a username Questions and Answers Aug 23, 2012
    Audience of 3 Million Users Receiving Anti-Sikh Messages Hard Talk Sep 17, 2010
    General How can I change my username ? Hard Talk Sep 4, 2010

  3. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    Do all the users have full access (Read, Write, eXecute and Delete) to the
    folder on the server where the back end resides?

    They must: the first user to connect to the database causes Access to create
    a locking file (.ldb) in that folder, subsequent users need to update that
    locking file, and the last user to exist causes Access to delete the locking
    file.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Mark" <mamacdon@dhr.state.ga.us> wrote in message
    news:1153414627.930736.298320@i3g2000cwc.googlegroups.com...
    > I have created a concurent user Access system with a front end on each
    > user's computer and a back end sitting on a common server. I am not
    > using the user level security. I have check that the dbf is shared and
    > row level record locking is enabled.
    >
    > More than one person can enter the system but the moment forms or
    > reports are accessed from the Switchboard error messages saying
    > somebody else has the table open in exclusive mode.
    >
    > How do I keep this from happening?
    >
    > Thanks for any help on this issue.
    >
     
  4. Mark

    Mark
    Expand Collapse
    Guest

    Yes Doug, all users have complete access r/w/x/d access to the be
    folder on the server.

    Just for the record, most folks in our IT group think MSAccess cannot
    be used concurrently and that is why this problem is occuring. Can
    more than one person access the tables on a back end? This issue is
    holding up implementation and I am totally stumped.

    Can you think of any other "switches", "flags" or coding I might need
    to set or tweak? Any books that might prove insightful?

    Thanks..


    Douglas J. Steele wrote:
    > Do all the users have full access (Read, Write, eXecute and Delete) to the
    > folder on the server where the back end resides?
    >
    > They must: the first user to connect to the database causes Access to create
    > a locking file (.ldb) in that folder, subsequent users need to update that
    > locking file, and the last user to exist causes Access to delete the locking
    > file.
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    > "Mark" <mamacdon@dhr.state.ga.us> wrote in message
    > news:1153414627.930736.298320@i3g2000cwc.googlegroups.com...
    > > I have created a concurent user Access system with a front end on each
    > > user's computer and a back end sitting on a common server. I am not
    > > using the user level security. I have check that the dbf is shared and
    > > row level record locking is enabled.
    > >
    > > More than one person can enter the system but the moment forms or
    > > reports are accessed from the Switchboard error messages saying
    > > somebody else has the table open in exclusive mode.
    > >
    > > How do I keep this from happening?
    > >
    > > Thanks for any help on this issue.
    > >
     
  5. Larry Linson

    Larry Linson
    Expand Collapse
    Guest

    "Mark" <mamacdon@dhr.state.ga.us> wrote

    > Yes Doug, all users have complete access
    > r/w/x/d access to the be folder on the server.


    > Just for the record, most folks in our IT
    > group think MSAccess cannot be used
    > concurrently and that is why this problem
    > is occuring. Can more than one person
    > access the tables on a back end?


    Yes, Access is inherently multi-user. {I spent some of my career working in
    or with IT departments, and I've never known any subject on which so many IT
    people were MISinformed as on Access!}

    Check once again to make sure the users have both Create and Delete
    authority for the shared folder in which the database and its LDB file
    reside.

    Check to make sure that none of the users opened the DB in exclusive mode.
    Create a desktop shortcut to open the DB, so you can specify the
    "parameters" of the command line statement.

    The Table supporting the Switchboard, if your switchboard was created using
    the Switchboard Manager, should be local to each user's computer -- not
    moved to the "Back End" with all the other tables. Personally, I find the
    Switchboard Manager-generated switchboards to be more trouble than they are
    worth (a complex solution to a simple problem, and don't ever use them
    except to demo to a user group that the SM exists). I create my own, using
    unbound forms, command buttons, and sometimes a few other controls to allow
    user's to select the record or range of records they want to view and/or
    edit.

    Larry Linson
    Microsoft Access MVP


    > This issue is holding up implementation
    > and I am totally stumped.
    >
    > Can you think of any other "switches", "flags" or coding I might need
    > to set or tweak? Any books that might prove insightful?
    >
    > Thanks..
    >
    >
    > Douglas J. Steele wrote:
    >> Do all the users have full access (Read, Write, eXecute and Delete) to
    >> the
    >> folder on the server where the back end resides?
    >>
    >> They must: the first user to connect to the database causes Access to
    >> create
    >> a locking file (.ldb) in that folder, subsequent users need to update
    >> that
    >> locking file, and the last user to exist causes Access to delete the
    >> locking
    >> file.
    >>
    >> --
    >> Doug Steele, Microsoft Access MVP
    >> http://I.Am/DougSteele
    >> (no e-mails, please!)
    >>
    >>
    >> "Mark" <mamacdon@dhr.state.ga.us> wrote in message
    >> news:1153414627.930736.298320@i3g2000cwc.googlegroups.com...
    >> > I have created a concurent user Access system with a front end on each
    >> > user's computer and a back end sitting on a common server. I am not
    >> > using the user level security. I have check that the dbf is shared and
    >> > row level record locking is enabled.
    >> >
    >> > More than one person can enter the system but the moment forms or
    >> > reports are accessed from the Switchboard error messages saying
    >> > somebody else has the table open in exclusive mode.
    >> >
    >> > How do I keep this from happening?
    >> >
    >> > Thanks for any help on this issue.
    >> >

    >
     
  6. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    "Larry Linson" <bouncer@localhost.not> wrote:

    >Check once again to make sure the users have both Create and Delete
    >authority for the shared folder in which the database and its LDB file
    >reside.


    To add to Larry's reply. Ensure each person can create a .txt file in
    that directory and delete it.

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     
  7. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    "Mark" <mamacdon@dhr.state.ga.us> wrote:

    >Just for the record, most folks in our IT group think MSAccess cannot
    >be used concurrently and that is why this problem is occuring. Can
    >more than one person access the tables on a back end? This issue is
    >holding up implementation and I am totally stumped.


    Absolutely. I have clients with 25 people using the backend. There
    are reliable reports of up to a hundred.

    There are some things you must do mind you.

    The three most common performance problems in Access 2000 or newer
    are:
    - LDB locking which a persistent recordset connection or an always
    open bound form corrects (multiple users)
    - sub datasheet Name property set to [Auto] should be [None]
    - Track name AutoCorrect should be off

    If the problem is for everyone when starting up the MDB then it likely
    needs a decompile.

    For more information on these, less likely causes, other tips and
    links to MS KB articles visit my Access Performance FAQ page at
    http://www.granite.ab.ca/access/performancefaq.htm

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     
  8. Ron2006

    Ron2006
    Expand Collapse
    Guest

    I have a more basic question. I do not know the answer, and will leave
    it with the MVPs to answer.

    In your first question you say:

    "I have created a concurent user Access system with a front end on each

    user's computer and a back end sitting on a common server. I am not
    using the user level security. I have check that the dbf is shared and

    row level record locking is enabled."

    Are you truely linked up to a DBF instead of an MDB.?

    MVPs: Does this make a difference? Can it make a difference.

    Ron
     
  9. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    "Ron2006" <ronnemec@hotmail.com> wrote:

    >I have a more basic question. I do not know the answer, and will leave
    >it with the MVPs to answer.
    >
    >In your first question you say:
    >
    >"I have created a concurent user Access system with a front end on each
    >
    >user's computer and a back end sitting on a common server. I am not
    >using the user level security. I have check that the dbf is shared and
    >row level record locking is enabled."
    >
    >Are you truely linked up to a DBF instead of an MDB.?
    >
    >MVPs: Does this make a difference? Can it make a difference.


    Excellent question. I never noticed those three letters before.
    <chuckle>

    And I have no idea of the answer as I've never used dbf's for anything
    but importing.

    TOny
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     

Share This Page