Results 1 to 4 of 4
  1. #1
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Cornwall, England
    Posts
    393
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Shared Development (XP)

    I am working on a project currently and keep getting the message

    <<database>> cant save design changes or save to a new database object because another user has the file open. To save your design changes or to save to a new object, you must have exclusive access to the file.

    how do i set up the database (or indeed the access installation) to allow multiple developers to work on the project?

    TIA

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Shared Development (XP)

    Starting with Access 2000, you must have exclusive access to the database in order to change the design of forms and reports. There is no workaround for this.

    In Access 97 and before, multiple users could be editing data and modifying the design of the database at the same time, but this was a dangerous feature. It could lead to unexpected behavior, changes disappearing into thin air and database corruption.

  3. #3
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Cornwall, England
    Posts
    393
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Shared Development (XP)

    Oh <img src=/S/sad.gif border=0 alt=sad width=15 height=15>

    Can see reasons why but would be good if it was an option that could be the developers choice.

    thanks anyway.

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

    Re: Shared Development (XP)

    Take it from me, the frustration of needing an exclusive lock on the database to change the design is not nearly as frustrating as spending a day overhauling a database and coming in the next morning to find that someone else had the database open, so their version overwrote all those changes. In that environment, I finally had to go around and check 25 machines to make sure none of them were still turned on to be sure my changes would be saved. If you need multiple developers working on a project, use a source control product like Source Safe (which has its own headaches) and only update the production database when all the changes are checked back into Source Safe. It's a bit more work, but you then have a history of versions and is the only way to control multiple developers. To make it work properly from Access, you need the Source Safe client which is part of the XP developer edition.
    Charlotte

Posting Permissions

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