Welcome to SPN

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

Sign Up Now!

Limit to One Instance

Discussion in 'Information Technology' started by rico, Oct 28, 2005.

Tags:
  1. rico

    rico
    Expand Collapse
    Guest

    I am running a database, simple mdb on a server which users then access using
    the Runtime. I want to know if there is a way to stop users opening more than
    instance on their computer, as this causes a few problems.

    TIA

    Rico
     
  2. Loading...

    Similar Threads Forum Date
    Opinion The Limitations of Being ‘Spiritual but Not Religious’ Breaking News Mar 23, 2013
    What actually are the 3 worlds? And is Maya limited only to the physical plane? Questions and Answers Nov 30, 2012
    Legal Cash Limit Breaking News Apr 4, 2012
    India Govt Mulls Proposal to Limit Number of Guests at Weddings Breaking News Feb 22, 2011
    The Limits of Free Will Interfaith Dialogues Feb 7, 2011

  3. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Hi, Rico.

    Please see the tip, "Preventing multiple instances of a database," on the
    following Web page:

    http://www.mvps.org/access/api/api0041.htm

    And if these users are sharing this MDB file, ensure that it's a split
    database, with the back end (tables and relationships) on the server and a
    copy of the front end (forms, queries, reports, et cetera) on each user's
    workstation, in order to reduce the likelihood of corruption and avoid other
    sticky issues as well.

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.

    (Please remove ZERO_SPAM from my reply E-mail address so that a message will
    be forwarded to me.)
    - - -
    If my answer has helped you, please sign in and answer yes to the question
    "Did this post answer your question?" at the bottom of the message, which
    adds your question and the answers to the database of answers. Remember that
    questions answered the quickest are often from those who have a history of
    rewarding the contributors who have taken the time to answer questions
    correctly.


    "rico" wrote:

    > I am running a database, simple mdb on a server which users then access using
    > the Runtime. I want to know if there is a way to stop users opening more than
    > instance on their computer, as this causes a few problems.
    >
    > TIA
    >
    > Rico
     
  4. rico

    rico
    Expand Collapse
    Guest

    Thanks Camaro,

    Out of interest: Currently i am not running a split database system,
    mainly because, users do not need thier own versions of the forms, its quick
    to do updates, and the fact that i haven't had any problems so far. I have
    thought about splitting the database, what are the advantages and what
    problems am i likely to run into if i dont split.

    Thanks alot

    Rico

    "'69 Camaro" wrote:

    > Hi, Rico.
    >
    > Please see the tip, "Preventing multiple instances of a database," on the
    > following Web page:
    >
    > http://www.mvps.org/access/api/api0041.htm
    >
    > And if these users are sharing this MDB file, ensure that it's a split
    > database, with the back end (tables and relationships) on the server and a
    > copy of the front end (forms, queries, reports, et cetera) on each user's
    > workstation, in order to reduce the likelihood of corruption and avoid other
    > sticky issues as well.
    >
    > HTH.
    > Gunny
    >
    > See http://www.QBuilt.com for all your database needs.
    > See http://www.Access.QBuilt.com for Microsoft Access tips.
    >
    > (Please remove ZERO_SPAM from my reply E-mail address so that a message will
    > be forwarded to me.)
    > - - -
    > If my answer has helped you, please sign in and answer yes to the question
    > "Did this post answer your question?" at the bottom of the message, which
    > adds your question and the answers to the database of answers. Remember that
    > questions answered the quickest are often from those who have a history of
    > rewarding the contributors who have taken the time to answer questions
    > correctly.
    >
    >
    > "rico" wrote:
    >
    > > I am running a database, simple mdb on a server which users then access using
    > > the Runtime. I want to know if there is a way to stop users opening more than
    > > instance on their computer, as this causes a few problems.
    > >
    > > TIA
    > >
    > > Rico
     
  5. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    There's a MUCH higher possibility of corruption when the database isn't
    split.

    As to the update issue, take a look at the free Auto FE Updater Tony Toews
    has at http://www.granite.ab.ca/access/autofe.htm

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


    "rico" <rico@discussions.microsoft.com> wrote in message
    news:FC54A88A-F42F-4F05-A2FA-65B017421AEF@microsoft.com...
    > Thanks Camaro,
    >
    > Out of interest: Currently i am not running a split database system,
    > mainly because, users do not need thier own versions of the forms, its

    quick
    > to do updates, and the fact that i haven't had any problems so far. I have
    > thought about splitting the database, what are the advantages and what
    > problems am i likely to run into if i dont split.
    >
    > Thanks alot
    >
    > Rico
    >
    > "'69 Camaro" wrote:
    >
    > > Hi, Rico.
    > >
    > > Please see the tip, "Preventing multiple instances of a database," on

    the
    > > following Web page:
    > >
    > > http://www.mvps.org/access/api/api0041.htm
    > >
    > > And if these users are sharing this MDB file, ensure that it's a split
    > > database, with the back end (tables and relationships) on the server and

    a
    > > copy of the front end (forms, queries, reports, et cetera) on each

    user's
    > > workstation, in order to reduce the likelihood of corruption and avoid

    other
    > > sticky issues as well.
    > >
    > > HTH.
    > > Gunny
    > >
    > > See http://www.QBuilt.com for all your database needs.
    > > See http://www.Access.QBuilt.com for Microsoft Access tips.
    > >
    > > (Please remove ZERO_SPAM from my reply E-mail address so that a message

    will
    > > be forwarded to me.)
    > > - - -
    > > If my answer has helped you, please sign in and answer yes to the

    question
    > > "Did this post answer your question?" at the bottom of the message,

    which
    > > adds your question and the answers to the database of answers. Remember

    that
    > > questions answered the quickest are often from those who have a history

    of
    > > rewarding the contributors who have taken the time to answer questions
    > > correctly.
    > >
    > >
    > > "rico" wrote:
    > >
    > > > I am running a database, simple mdb on a server which users then

    access using
    > > > the Runtime. I want to know if there is a way to stop users opening

    more than
    > > > instance on their computer, as this causes a few problems.
    > > >
    > > > TIA
    > > >
    > > > Rico
     
  6. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Hi, Rico.

    > Currently i am not running a split database system,
    > mainly because, users do not need thier own versions of the forms


    If these are bound forms, then the users should have their own copy,
    especially if there are Memo/OLE data type fields that the form is bound to.
    An interrupted "write to disk" operation is what usually causes corruption,
    and multiple users sharing bound forms are known to bring higher risk of
    these errors.

    > its quick
    > to do updates,


    One can automate the distribution of the front end with Tony Toews's (MVP)
    AutoFE utililty. With this utility, the developer places the new front end
    on the server and the next time the users open the application, the new
    front end is saved to their hard drives and they start using it. Please see
    the following Web page for more information on his utility:

    http://www.granite.ab.ca/access/autofe.htm

    > and the fact that i haven't had any problems so far.


    Famous last words. ;-) There's no guarantee that this will remain the
    case. Most work places want to minimize the down time for database
    applications, so the first recommendation for multiuser databases is to
    split the database as a precaution against the likelihood of corruption.
    For more information, please see the tip on split databases on the following
    Web page:

    http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB

    > what are the advantages and what
    > problems am i likely to run into if i dont split.


    Besides what's discussed in the tip listed above, I'll add that you've been
    lucky so far that you haven't had any problems. The Microsoft Access team
    has admitted that the number one cause of curruption is the sharing of
    multiuser databases.

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.


    "rico" <rico@discussions.microsoft.com> wrote in message
    news:FC54A88A-F42F-4F05-A2FA-65B017421AEF@microsoft.com...
    > Thanks Camaro,
    >
    > Out of interest: Currently i am not running a split database system,
    > mainly because, users do not need thier own versions of the forms, its
    > quick
    > to do updates, and the fact that i haven't had any problems so far. I have
    > thought about splitting the database, what are the advantages and what
    > problems am i likely to run into if i dont split.
    >
    > Thanks alot
    >
    > Rico
    >
    > "'69 Camaro" wrote:
    >
    >> Hi, Rico.
    >>
    >> Please see the tip, "Preventing multiple instances of a database," on the
    >> following Web page:
    >>
    >> http://www.mvps.org/access/api/api0041.htm
    >>
    >> And if these users are sharing this MDB file, ensure that it's a split
    >> database, with the back end (tables and relationships) on the server and
    >> a
    >> copy of the front end (forms, queries, reports, et cetera) on each user's
    >> workstation, in order to reduce the likelihood of corruption and avoid
    >> other
    >> sticky issues as well.
    >>
    >> HTH.
    >> Gunny
    >>
    >> See http://www.QBuilt.com for all your database needs.
    >> See http://www.Access.QBuilt.com for Microsoft Access tips.
    >>
    >> (Please remove ZERO_SPAM from my reply E-mail address so that a message
    >> will
    >> be forwarded to me.)
    >> - - -
    >> If my answer has helped you, please sign in and answer yes to the
    >> question
    >> "Did this post answer your question?" at the bottom of the message, which
    >> adds your question and the answers to the database of answers. Remember
    >> that
    >> questions answered the quickest are often from those who have a history
    >> of
    >> rewarding the contributors who have taken the time to answer questions
    >> correctly.
    >>
    >>
    >> "rico" wrote:
    >>
    >> > I am running a database, simple mdb on a server which users then access
    >> > using
    >> > the Runtime. I want to know if there is a way to stop users opening
    >> > more than
    >> > instance on their computer, as this causes a few problems.
    >> >
    >> > TIA
    >> >
    >> > Rico
     

Share This Page