Navision Attain Server

markusmathis

We run Navision Attain 3.10 on a server for development. This works fine as long as only one progammer is working on the database. If there is more than one developer working at the same time, the objects from programmer A aren't updated for programmer B. That means that one programmer has updated objects whereas the other programmer only has the "old" objects, which aren't up to date.

This worked fine with Navision Financials 2.60. Is there any solution on this problem?

---

Luc_VanDyck

You can try setting the objectcache for the client to 0. This way, Navision has to read the object every time it is opened.

Or use the tool Window Watcher (available in the download-section) to keep an eye on modified objects.

bostjanl

markusmathis wrote:

We run Navision Attain 3.10 on a server for development. This works fine as long as only one progammer is working on the database. If there is more than one developer working at the same time, the objects from programmer A aren't updated for programmer B. That means that one programmer has updated objects whereas the other programmer only has the "old" objects, which aren't up to date.

This worked fine with Navision Financials 2.60. Is there any solution on this problem?

---

As Luc wrote, use WindowsWatcher. Our company used it for almost 2 years now and so far we did'n overwrite eachothers objects.


Bostjan

DenSter

The only way to really avoid losing object is for each developer to have their own database, tag all their changes and have good object management procedures in place. Even if someone overwrites someone else's work, you still have that work in a fob file, or in the developer's local database. The procedures should make it so you discover object conflicts before they occur (IF every developers tags their work correctly)