Concurrent Developers in MS Access 2007

Is there a way to allow concurrent multiple developersin MS Access 2007?
Who is Participating?
Dale FyeCommented:
I'm not aware of a tool that would allow you develop concurrently and check objects in and out, like Visual Source Safe .  

However, as long as you were working on completely independent tasks, you could work in tandem with each developer maintaining their objects code and forms, and then import from one to another to create your next baseline.

Once you create a new baseline, everyone continues to work off of it, saving their changes to their own version, and when ready, you create another baseline.  This would require very careful planning, coordination, and execution.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Be careful with VSS and Access. While you can checkout objects and work with them independently, there are some issues with SS and Access. I tried this route with 2003, and ended up in a bigger mess than when I started - corrupt database, versioning issues (i.e changes made by UserA were overwritten by UserB with no notice), etc etc. From my experience, VSS and Access is not a good fit.

Just my .02, and you may have much better luck than I.

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:

  No.  As far as VSS, a few that have worked with it have remarked that it didn't work all that well.  Don't remember specific comments, just that it seemed to be more bother then it was worth.

Dale FyeCommented:
Upon further reading, I notice you have to purchase Visual Source Safe for the solution posted by Nicobo, you might want to consider "SourceAnywhere for Access 2007"
leeroypitreAuthor Commented:
We do not have VSS.  Can multipe developers work on an MS Access 2007 concurrently?
leeroypitreAuthor Commented:
When multiple people try to modify different objects it does not let us stating the administrator has it locked.
Dale FyeCommented:
Like I said previously.  As long as each developer is working on completely independent tasks, that involve no overlap (not modifying code on the same form, report, query, or code module) and no modifications to the database structure, users can work independently of one another(on their own version of the application), and can merge their projects (import objects into a master) as time goes along.

But this requires very careful planning, coordination, and execution.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
To be clear, UserA can work on the SAME Database exclusively. UserB could NOT open the SAME file, even to work on different objects. As fyed has said, you would need to manage multiple copies of Access and merge the changes into a master database.

If you need concurrent development, I'd encourage you to move to a different platform, like one of the .NET languages, PHP, etc etc. Those fully support multiple developers. Even then, however, you'll have to have some form of source control. There are some free ones out there, of course, so you could perhaps use one of those.
As everyone has noted this is not supported in Access.
With incredible discipline, good communication and luck you could build something to facilitate it.
No two users can open and alter an MS Access database at the same time.
You would therefore need a folder named 'Master', with a master copy of the file in it.

Each developer would make a new copy after each build in another folder on each developer's machine, call it folder 'Dev.'
Each developer would have to communicate to the others what objects he/she intends to alter.
When your task is complete you would export your altered objects back to 'master' and delete 'dev'
The next task, you would repeat the process.

If you don't have luck and communication, two developers will alter the same object.
Whoever exports last will have their code in the master file.

With coding and discipline, you could automate the export of altered objects.
Version numbers could be stored in the tag property of objects that support that.
Some other method for objects that don't support that could be devised
Pehaps a table with object names and versions.
The export code could check to see if the object being exported had been altered by others since the session began.
It would export and update objects that were unchanged, flag conflicts, and update version numbers

It will be a constant headache and a whack of planning and coding.

Another method would be to break the objects in 'Master' exclusively into a number of 'dev' files.
All the reports in one, queries in another, forms in a third ect
Or perhaps by object dependencies
The other objects would be made hidden, perhaps.

Objects you changed would be pushed to 'master'
Editable objects would be pulled from it

Still a headache.
Still a whack of coding.

But doable
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.