Codeunit Sync Problem

Emmanuel · 2006-12-14

We're having a problem with synchronization of codeunits modified on SQL database. Here's the problem, we're 2 developers working on NAV 3.7 with SQL 2000, if I modify a codeunit, the only way the other developer can see the change is by closing and restarting navision. Is there an option or setting to cure this problem.

HalMdy · 2006-12-14

I think CodeUnits are stored in the local Object cache. If you reduce the cache, you have more chance to see the changes ...

Otherwise, no solution ...
Note : it's the same with a native server .

Emmanuel · 2006-12-14

Thank you that worked, I was on the right track, I had reduced it to 0 but did not close navision, just reopened the DB and it did not seem to work, now I set it to 1 on both machines restarted Navision and problem solved.

kriki · 2006-12-14

If you work on Navision in more developers, it is best that each works in it's own DB and that you swap fob-files between them. I have worked like this before and I have had very few problems. Working on the same DB has given me a lot more problems.
They best have the format
CUSTOMER 400SP2 YYYYMMDD HHMMSS some description.fob.

In this way you have a follow up of development and they are easily ordered.
Navision (and now Microsoft) advice to work in different DB's.

Waldo · 2006-12-14

Object cache = 0 is a must for working with 2 developers in 1 db.

Furthermore,
I heard once of a solution (I think it's somewhere in this forum as well) by SQL triggers. Locking an object, unlocking ... it's all done on SQL level (triggers).

Check this out:
http://www.mibuso.com/dlinfo.asp?FileID=773

Codeunit Sync Problem

Comments

Categories