Welcome to SPN

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

Sign Up Now!

Using application from a network

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

  1. JoeA2006

    JoeA2006
    Expand Collapse
    Guest

    I have placed an Access database in a network folder allowing multiple users
    to view and use the database. What is the best way to prevent network
    problems from affecting the data being input into the database? Basically, I
    would like to be sure as much data as possible is saved, in case of a network
    problem.
     
  2. Loading...


  3. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    If you haven't already, split your application into a front-end (containing
    the queries, forms, reports, macros and modules) and a back-end (containing
    the tables and relationships). Each user should have his/her copy of the
    front-end, ideally on the hard drive of his/her computer. Only the back-end
    should be on the server. That will significantly reduce the possibility of
    database corruption.

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


    "JoeA2006" <JoeA2006@discussions.microsoft.com> wrote in message
    news:7C71255B-9620-490C-8454-1EB998F44E39@microsoft.com...
    > I have placed an Access database in a network folder allowing multiple

    users
    > to view and use the database. What is the best way to prevent network
    > problems from affecting the data being input into the database? Basically,

    I
    > would like to be sure as much data as possible is saved, in case of a

    network
    > problem.
    >
    >
     
  4. Jerry Whittle

    Jerry Whittle
    Expand Collapse
    Guest

    1. Split the database into a front end with the forms, reports, etc., and a
    back end with just the tables. Ideally each user gets a copy of the FE on
    their computer. Access comes with a Database Splitter tool.

    2. Under Tools, Options, Advanced tab make sure that the Default Open Mode
    is Shared and Default Record Locking is Edited Record.

    3. Make sure that all users have full privileges to the network folder
    holding the database file. They all need Read, Write, Create, and Delete for
    the entire folder.

    4. Backup the database frequently to either your PC, tape, or another
    network drive on a different hard drive. Nothing beats a current backup when
    things go bad.

    5. To prevent database corruption problems see if your network people will
    run a sniffer to look for bad packets and other network problems. If there is
    a problem, Access will fall victum to it. A sniffer is somewhat expensive.
    --
    Jerry Whittle
    Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


    "JoeA2006" wrote:

    > I have placed an Access database in a network folder allowing multiple users
    > to view and use the database. What is the best way to prevent network
    > problems from affecting the data being input into the database? Basically, I
    > would like to be sure as much data as possible is saved, in case of a network
    > problem.
    >
    >
     
  5. JoeA2006

    JoeA2006
    Expand Collapse
    Guest

    I tried to use the database splitter and recieve a "Subscript out of range"
    error. Do I have too many objects? It looks like the tables got placed into a
    new backend and then threw the error. I could eliminate some of the objects
    if need be. I am running Access 2000 9.0 SP-3 on Windows XP Pro. Can I
    accomplish the same thing by manually importing forms and reports into
    another database?

    "Jerry Whittle" wrote:

    > 1. Split the database into a front end with the forms, reports, etc., and a
    > back end with just the tables. Ideally each user gets a copy of the FE on
    > their computer. Access comes with a Database Splitter tool.
    >
    > 2. Under Tools, Options, Advanced tab make sure that the Default Open Mode
    > is Shared and Default Record Locking is Edited Record.
    >
    > 3. Make sure that all users have full privileges to the network folder
    > holding the database file. They all need Read, Write, Create, and Delete for
    > the entire folder.
    >
    > 4. Backup the database frequently to either your PC, tape, or another
    > network drive on a different hard drive. Nothing beats a current backup when
    > things go bad.
    >
    > 5. To prevent database corruption problems see if your network people will
    > run a sniffer to look for bad packets and other network problems. If there is
    > a problem, Access will fall victum to it. A sniffer is somewhat expensive.
    > --
    > Jerry Whittle
    > Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
    >
    >
    > "JoeA2006" wrote:
    >
    > > I have placed an Access database in a network folder allowing multiple users
    > > to view and use the database. What is the best way to prevent network
    > > problems from affecting the data being input into the database? Basically, I
    > > would like to be sure as much data as possible is saved, in case of a network
    > > problem.
    > >
    > >
     

Share This Page