Welcome to SPN

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

Sign Up Now!

Database corruption

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

  1. steve p

    steve p
    Expand Collapse
    Guest

    I have a network database which is accessed by approx. 15 users, plus 3 which
    connect through Terminal Server. The database is currently split into a front
    end, and a back end, and each workstation has a copy of the front end on
    their own computer. The size of the back end is around 75 Mb. This database
    has been up and running for the past 5 or 6 years.

    The problem that I am having is with database corruption. Over the years, I
    can probably count on one hand how many times the tables have became corrupt.
    Since the start of this year, the tables have been corrupted at least 7
    times, and now it seems to be a weekly occurrence. Is this a sign of
    impending doom? Should I be looking to upgrade to SQL Server? I have not
    found a good estimate to the maximum number of connections to an Access
    database, but I would have trouble believing that I am maxed out with 18
    users.

    One thought that I have has to do with the design of the front end. I
    inherited alot of this code, so some may not be "perfect code." The one thing
    that sticks out in my mind is the opening of a recordset, and then never
    closing it. I can see this not causing a major problem with a smaller
    database, maybe the occasional corruption. But as the tables grow, the
    problem would grow exponentially. Is this correct? Is this a possible root of
    my problem?

    Any thoughts would be appreciated.

    Thanks in advance.
     
  2. Loading...

    Similar Threads Forum Date
    USA NSA has massive database of Americans' phone calls (USA Today 5.11.2006) Breaking News Jun 11, 2013
    Some database errors while navigating SPN forums Announcements Dec 29, 2004
    India Corruption rate in India is double of global average Breaking News Jul 9, 2013
    Partition Corruption in the Punjab... History of Sikhism Mar 24, 2013
    Bant Singh - A real anti-corruption hero Inspirational Stories Feb 27, 2013

  3. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    You might want to read the Corrupt Microsoft Access MDBs FAQ that Tony Toews
    has at http://www.granite.ab.ca/access/corruptmdbs.htm

    Have you got new hardware on your network? Access has often been described
    as the canary for network problems, especially flaky NICs.

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


    "steve p" <stevep@discussions.microsoft.com> wrote in message
    news:2C0D093A-4E3E-4E6E-9B5E-E5198914A699@microsoft.com...
    > I have a network database which is accessed by approx. 15 users, plus 3

    which
    > connect through Terminal Server. The database is currently split into a

    front
    > end, and a back end, and each workstation has a copy of the front end on
    > their own computer. The size of the back end is around 75 Mb. This

    database
    > has been up and running for the past 5 or 6 years.
    >
    > The problem that I am having is with database corruption. Over the years,

    I
    > can probably count on one hand how many times the tables have became

    corrupt.
    > Since the start of this year, the tables have been corrupted at least 7
    > times, and now it seems to be a weekly occurrence. Is this a sign of
    > impending doom? Should I be looking to upgrade to SQL Server? I have not
    > found a good estimate to the maximum number of connections to an Access
    > database, but I would have trouble believing that I am maxed out with 18
    > users.
    >
    > One thought that I have has to do with the design of the front end. I
    > inherited alot of this code, so some may not be "perfect code." The one

    thing
    > that sticks out in my mind is the opening of a recordset, and then never
    > closing it. I can see this not causing a major problem with a smaller
    > database, maybe the occasional corruption. But as the tables grow, the
    > problem would grow exponentially. Is this correct? Is this a possible root

    of
    > my problem?
    >
    > Any thoughts would be appreciated.
    >
    > Thanks in advance.
     

Share This Page