Welcome to SPN

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

Sign Up Now!

Access with Multi-User

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

  1. Paola

    Paola
    Expand Collapse
    Guest

    Is the quickest way to fix issues brought from more than one user in an
    access db to move the tables to sql and link them to the access db file?
    Any recommendations on the quickest most effective way?

    Thanks,
    Paola
     
  2. Loading...


  3. Steve Schapel

    Steve Schapel
    Expand Collapse
    Guest

    Paola,

    Access is built to work in a multi-user environment. Moving tables to
    SQL Server (I presume that's what you meant) is unlikely to solve the
    problem. What is the problem you are experiencing?

    I guess the first thing to check is whether you have the core data in a
    separate backend mdb file, and each user linking to these tables from
    their own local copy of the application (frontend) file?

    --
    Steve Schapel, Microsoft Access MVP

    Paola wrote:
    > Is the quickest way to fix issues brought from more than one user in an
    > access db to move the tables to sql and link them to the access db file?
    > Any recommendations on the quickest most effective way?
    >
    > Thanks,
    > Paola
     
  4. Norman Yuan

    Norman Yuan
    Expand Collapse
    Guest

    Some issues with Access app "brought up by more than one user" does not mean
    you need to move data from Jet DB to SQL Server. An access app with table
    linked to SQL Server would still have issues "brought up buy more than one
    user". It all depends on what the issues are. So, it does not make sense to
    recormmend/find a quickest/most effective way without carefully analysing
    the issues.

    "Paola" <Paola@discussions.microsoft.com> wrote in message
    news:19D856AB-A386-4CBE-B074-CD4370CEDFD1@microsoft.com...
    > Is the quickest way to fix issues brought from more than one user in an
    > access db to move the tables to sql and link them to the access db file?
    > Any recommendations on the quickest most effective way?
    >
    > Thanks,
    > Paola
     
  5. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

  6. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    I agree with Norman, Steve and Albert.

    Here is an article that you might find helpful:
    Implementing a Successful Multiuser Access/JET Application
    http://www.access.qbuilt.com/html/multiuser_applications.html


    If you decide that you really need to migrate, you should obtain a copy of
    the book titled "Microsoft Access Developer's Guide to SQL Server", written
    by Mary Chipman and Andy Baron (SAMS Publishing). Here is a link to the book
    at Amazon.com:

    http://www.amazon.com/exec/obidos/t...103-5399559-8631817?v=glance&s=books&n=507846

    Early in the book (page 6) the authors write:

    <Begin Quote>
    "Many people think that upsizing from the Jet database engine to SQL Server
    is a universal panacea for whatever is ailing their Access databases. It's
    not. In fact, just the opposite is usually true. If your Access application
    is a dog, then most likely it will still be a dog after you upsize it to SQL
    Server--perhaps an even bigger, uglier, shaggier dog! Even a well-designed
    Jet database often won't run any faster after the tables are upsized to SQL
    Server if you are using the same data access methods you used for your Access
    database. In order to successfully convert your Access database, you have to
    be clear about why it needs to be upsized, and you need to understand how to
    take advantage of the strengths of SQL Server by reworking the data access
    elements of your Access application."
    </End Quote>


    Tom Wickerath
    Microsoft Access MVP

    http://www.access.qbuilt.com/html/expert_contributors.html
    http://www.access.qbuilt.com/html/search.html
    __________________________________________

    "Norman Yuan" wrote:

    > Some issues with Access app "brought up by more than one user" does not mean
    > you need to move data from Jet DB to SQL Server. An access app with table
    > linked to SQL Server would still have issues "brought up buy more than one
    > user". It all depends on what the issues are. So, it does not make sense to
    > recormmend/find a quickest/most effective way without carefully analysing
    > the issues.

    __________________________________________

    > "Paola" <Paola@discussions.microsoft.com> wrote in message
    > news:19D856AB-A386-4CBE-B074-CD4370CEDFD1@microsoft.com...


    > > Is the quickest way to fix issues brought from more than one user in an
    > > access db to move the tables to sql and link them to the access db file?
    > > Any recommendations on the quickest most effective way?
    > >
    > > Thanks,
    > > Paola
     

Share This Page