Multiple Developers...Source Control

[dcroe05]

I'm having a problem using an Access database in Source Safe.

How do we get around the problem of letting multiple users have access to the database so that more than one person can make changes.

If one user opens the databse so that they can check out an object and make changes to that object, they have to open the database exclusively. So a second programmer can't open the database.

This just isn't an improvement over the standard Access functionality.

Does anyone know how to get around this? Is there another program that can help us accomplish this?

 

[BobStubbs]

I would organise development like this:

-- Start with the 'live' database - in production.
-- There's a need to change an object (say, a form)
-- Take a copy of 'live', call this 'development1'
-- Programmer works on the form in 'development1', changes it, and tests it
-- When changes are signed off, the live database is taken off-line (normally out of hours), while the new version of the form object is imported into it - a quick process.
-- The live database is then copied again , as required, for further development.

Two or more programmers can work on two or more objects at the same time, in different 'development' copies, provided that they do not need to change the same underlying table - you need a management process to control this.

I think that's the best you can do with Access ... does anyone else have a suggestion?

Bob Stubbs (London, UK)