Welcome to SPN

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

Sign Up Now!

Problem with Access Database Crashing?

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

  1. Advo

    Advo
    Expand Collapse
    Guest

    Hi There. Currently at work, we have a database which is used by
    multiple users. Its about 24mb and connects to our SQL database, mainly
    just use access for the forms and so on. This database front end is
    probably used by about 15 employee's and runs from our server, in this
    case SRV2.

    The problem is, now and again, the access database will die for a user,
    i.e. they will try and load the database, and it gives them error
    messages saying that it needs to be repaired. If they click yes, then
    they still arent allowed to do it.

    This is where the pain arises. In order to fix the database, we have to
    get everyone off the access database, and then go to our SRV2 server,
    load the database, and then repair it.. this is fine and users can then
    go back onto the database.

    This isnt ideal, and is happening more and more often. Anyone got any
    ideas why, or ways to solve this problem?

    Thanks
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News Sikhs Face Problems While Carrying Kirpans In Khyber-Pakhtunkhwa - SikhSiyasat.Net Breaking News Jul 29, 2016
    "Dasam" Granth - A Look At The Core Problems Dasam Granth Oct 21, 2015
    Problems In Life Sikh Sikhi Sikhism Apr 13, 2015
    How can I make decent and useful friends and from where ?? most people have a problem with me Sikh Youth Oct 23, 2013
    The Problem with Taking Too Many Vitamins Health & Nutrition Oct 18, 2013

  3. Rick Brandt

    Rick Brandt
    Expand Collapse
    Guest

    Advo wrote:
    > Hi There. Currently at work, we have a database which is used by
    > multiple users. Its about 24mb and connects to our SQL database,
    > mainly just use access for the forms and so on. This database front
    > end is probably used by about 15 employee's and runs from our server,
    > in this case SRV2.
    >
    > The problem is, now and again, the access database will die for a
    > user, i.e. they will try and load the database, and it gives them
    > error messages saying that it needs to be repaired. If they click
    > yes, then they still arent allowed to do it.
    >
    > This is where the pain arises. In order to fix the database, we have
    > to get everyone off the access database, and then go to our SRV2
    > server, load the database, and then repair it.. this is fine and
    > users can then go back onto the database.
    >
    > This isnt ideal, and is happening more and more often. Anyone got any
    > ideas why, or ways to solve this problem?
    >
    > Thanks


    Each user should have their own (local) copy of the file. Having multiple users
    in the same file causes exactly what you are seeing.


    --
    Rick Brandt, Microsoft Access MVP
    Email (as appropriate) to...
    RBrandt at Hunter dot com
     
  4. Advo

    Advo
    Expand Collapse
    Guest

    Rick Brandt wrote:
    > Advo wrote:
    >
    >>Hi There. Currently at work, we have a database which is used by
    >>multiple users. Its about 24mb and connects to our SQL database,
    >>mainly just use access for the forms and so on. This database front
    >>end is probably used by about 15 employee's and runs from our server,
    >>in this case SRV2.
    >>
    >>The problem is, now and again, the access database will die for a
    >>user, i.e. they will try and load the database, and it gives them
    >>error messages saying that it needs to be repaired. If they click
    >>yes, then they still arent allowed to do it.
    >>
    >>This is where the pain arises. In order to fix the database, we have
    >>to get everyone off the access database, and then go to our SRV2
    >>server, load the database, and then repair it.. this is fine and
    >>users can then go back onto the database.
    >>
    >>This isnt ideal, and is happening more and more often. Anyone got any
    >>ideas why, or ways to solve this problem?
    >>
    >>Thanks

    >
    >
    > Each user should have their own (local) copy of the file. Having multiple users
    > in the same file causes exactly what you are seeing.
    >
    >



    Could that just be fixed then by creating a copy of that main file on
    our server, and distributing that to each single user?
     
  5. Rick Brandt

    Rick Brandt
    Expand Collapse
    Guest

    "Advo" <x@x.com> wrote in message
    news:KFgqg.11931$v4.1832@newsfe3-win.ntli.net...
    > Rick Brandt wrote:
    >> Advo wrote:
    >>
    >>>Hi There. Currently at work, we have a database which is used by
    >>>multiple users. Its about 24mb and connects to our SQL database,
    >>>mainly just use access for the forms and so on. This database front
    >>>end is probably used by about 15 employee's and runs from our server,
    >>>in this case SRV2.
    >>>
    >>>The problem is, now and again, the access database will die for a
    >>>user, i.e. they will try and load the database, and it gives them
    >>>error messages saying that it needs to be repaired. If they click
    >>>yes, then they still arent allowed to do it.
    >>>
    >>>This is where the pain arises. In order to fix the database, we have
    >>>to get everyone off the access database, and then go to our SRV2
    >>>server, load the database, and then repair it.. this is fine and
    >>>users can then go back onto the database.
    >>>
    >>>This isnt ideal, and is happening more and more often. Anyone got any
    >>>ideas why, or ways to solve this problem?
    >>>
    >>>Thanks

    >>
    >>
    >> Each user should have their own (local) copy of the file. Having multiple
    >> users in the same file causes exactly what you are seeing.
    >>
    >>

    >
    >
    > Could that just be fixed then by creating a copy of that main file on our
    > server, and distributing that to each single user?


    Sure. You might want to check out the free utility that Tony Toews provides
    that would automatically push new updates to each user if you ever update the
    file on the server.

    --
    Rick Brandt, Microsoft Access MVP
    Email (as appropriate) to...
    RBrandt at Hunter dot com
     
  6. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    Advo <x@x.com> wrote:

    >Could that just be fixed then by creating a copy of that main file on
    >our server, and distributing that to each single user?


    Yes, but that would be network traffic than each user having their own
    copy on their hard drive.

    I specifically created the Auto FE Updater utility so that I could
    make changes to the FE MDE as often as I wanted and be quite confident
    that the next time someone went to run the app that it would pull in
    the latest version. For more info on the errors or the Auto FE
    Updater utility see the free Auto FE Updater utility at
    http://www.granite.ab.ca/access/autofe.htm at my website to keep the
    FE on each PC up to date.

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     

Share This Page