Results 1 to 6 of 6
  1. #1
    2 Star Lounger
    Join Date
    May 2001
    Location
    Wichita, Kansas, USA
    Posts
    177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Editing shared database (Access 2000)

    I have done a search on this topic on Woody's, but can't seem to find related posts:
    We recently upgraded our office from Access 97 to Access 2000. We have several databases that are used by multiple users at once, off a shared drive.
    However, Access 2000 won't let us edit the database in any way as long as someone has it open. In Access 97, you used to be able to, for instance, edit a form, as long as no one was in that particular form or part of the database. But Access 2000 won't let you edit ANY of it as long as someone else has any part of the database open.

    Is there any way around this?
    Tracy

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Editing shared database (Access 2000)

    What you said is true for forms, reports, macros and modules in Access 2000. It was a conscious design decision by MS to no longer allow those kinds of changes - doing as you suggest in Access 97 can cause problems if two people make changes to the same form or report. When we converted, we bit the bullet and deployed the front-end for all databases to the workstation. It also gives you the benefit of improved response times, as the local front-end will almost always load a fair bit quicker. It does create a significant lodgistics problem if you have 60 or 100 users as we often do - solving that issue is a subject of a number of threads in the last year or so. Feel free to reply if you have further questions about the issues.
    Wendell

  3. #3
    2 Star Lounger
    Join Date
    May 2001
    Location
    Wichita, Kansas, USA
    Posts
    177
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Editing shared database (Access 2000)

    Thanks Wendell.
    This is also what I was finding out by reading Microsoft's Knowledge Database. Apparently I will need to go load a front-end on each users' station in order to share it properly. The down side of this is that if one editor creates a new form or report on her copy of the front-end, no one else will have that same form or report, correct? (Unless I copy it over to other front-ends).

    Tracy

  4. #4
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Edmonton, Alberta, Canada
    Posts
    326
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Editing shared database (Access 2000)

    I regularly ran into problems with Access 97 corrupting databases (the front-ends only, almost never the back-ends) when a report or form was edited while someone else was in the database even when there was no possibility that anyone else was trying to use the form or report in question (a small enough group of people use our databases that it was possible to guarantee that no one was trying to use a given report or form). So, with Access 97, our philosophy rapidly became "Don't make anychanges to a database that someone else is using!". From our point of view, the fact that Access 2000 enforces that is a feature, other than the fact that it tends to leave a database locked exclusively longer than it needs to.

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Editing shared database (Access 2000)

    I believe that was one of the reasons behind that decision. Another problem in 97 was that you didn't always know that someone else had a database open (i.e., midnight and you're the only one in the place but some moron left their database open). I was deeply annoyed many times when changes I had made disappeared the next day because the last one who saved won! My design changes got overwritten when someone else closed the database after I had gotten out. <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23>
    Charlotte

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Editing shared database (Access 2000)

    Your "down-side" is correct - if users are creating new objects, then you need to have a method for getting them centralized and redeployed. We actually use a deployment tool we developed to make the process easier. We also create small ad hoc databases where people can play and create objects if they really want to (and are capable of doing so with out destroying data). We do all of our development against a test database and use Source Safe, since there are between 3 and 5 developers working on various projects. It just got to be too complicated to keep track of all the design changes folks were making. Hope this helps you understand some of the options.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •