Our dev team typically services up the database when they are developing a project with multiple developers for easier and faster integration testing. They claim they don't have problems with mulitple developers trying to change the same objects because they follow a build plan. Each person is assigned to modify/create different objects. The work is "properly partitioned." I would not be surprised if Navision can't see the need for this because they have the same attitude about how development SHOULD be done.
Never-the-less, this problem is real and some teams have it. What if every time you were going to work in an object, you edit the version number and put your initials in the front of the other versions? At least that would be a simple system to inform others that you intended to change the object.
Since we are dreaming about changes to the development system, I sure wish Navision would save all the versions of all the objects. Perhaps with some sort of purge function. We use Visual Source safe for version management. However, it really would be great if this was integrated into the dev environment.
Jim Hollcraft
NCSD, NCSP, MCSE, CNE, MCP, MST
aka Skater
http://drilldot.com
Unauthorized Navision News
Jim Hollcraft