Welcome to SPN

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

Sign Up Now!
  1. Guest ji, please consider donating today!
      Become a Supporter    ::   Make a Contribution   
    Monthly Recurring Target: $300 :: Achieved: $95

Sharing Issues of Access 2002 on a Server?

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

  1. Gary

    Gary
    Expand Collapse
    Guest

    I will have an access 2002 application on a shared server. Can I have
    multiple users using the same problem concurrently and updating the same
    tables???

    Will Access 2002 handle the issue of sharing with multiple users???

    If so, how (general concepts).


    It it can't be shared on a server, does anyone have possible suggestions???


    Thanks You,

    Gary
     
  2. Loading...

    Similar Threads Forum Date
    Sikhi VAND CHHAKNA: The Sikh Way Of Sharing & Caring Sikh Sikhi Sikhism Dec 3, 2015
    Sharing A Bit About My Journey Into Sikhi New to Sikhism Aug 30, 2014
    India Sounding the alarm on wife-sharing Breaking News Nov 10, 2011
    India "Wife-sharing" haunts Indian villages as girls decline Breaking News Oct 28, 2011
    Legal Sharing Passwords with Spouse is Risky Breaking News Oct 14, 2011

  3. Larry Linson

    Larry Linson
    Expand Collapse
    Guest

    "Gary" <Gary@discussions.microsoft.com> wrote

    > I will have an access 2002 application on a
    > shared server. Can I have multiple users using
    > the same problem concurrently and updating
    > the same tables???


    Yes, you can, but see below.

    > Will Access 2002 handle the issue of sharing with multiple users???


    Yes, usually.

    > If so, how (general concepts).


    Access is, out of the box, multiuser capable.

    You may run for a long time without problems, but having multiple users
    logged in to the same front-end or monolithic database significantly
    increases the chances of corruption. Thus, the standard suggested solution
    is to split the tables (back-end: tables and relationships) and store them
    on the server, but put a separate copy of the user interface (front-end:
    queries, forms, reports, macros, modules) on each user's machine.

    Distributing and updating the front-end is simplified by MVP Tony Toews'
    Front End Updater... http://www.granite.ab.ca/accsmstr.htm. However, I have
    had good luck with the simpler approach that you'll find at
    http://accdevel.tripod.com.

    Larry Linson
    Microsoft Access MVP
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page