importing or re-compling objects in use

Steve_Contris

Is there any problem with importing forms or tables that may be in use by other clients on the network? I have noticed that at times they may receive a message about the form having been updated while they were using it but all they had to do was close and reopen the form. At other times some changes did not seem to show up until re-starting navision.
Other than that, things seem to import without problems even if they are in use somewhere.

themave

some forms are held in the local cache and thus they don't get updated until the user closes and reopens Navision, depending on the user cache setting and what is in it, sometimes the form is flushed and updated before they close and reopen, at least that is my best guess at it.

I noticed the same thing.

thaug

I've mentioned this before, but be careful with importing/compiling objects in 4.0 when users are on the system potentially using that form. I used to be able to do that while users were on, and it would just kick them out of the form. However, in 4.0 SP1, importing objects mid-stream caused clients to crash randomly. MS was no help. Only waiting until everyone was off and compiling all objects was I able to fix the problem.

I also found it necessary to set the Object Cache to 0 when we went live with 4.0 to guarantee that clients were not using older versions of objects.

kriki

Strange. I never (from 1.2 to 4.00SP2) had problems importing forms when people are working. The keep on using the old form. If you import tables, you can get messages because they can change the table enough (adding a field, change the type of a field) so Navision says they have an old version of the table and give that error. Closing the DB on the client and reopening it fixes the problem.
This last problem happens a lot less with a SQL-DB.

thaug: never put the cache to 0, because this can be VERY bad for performance. Especially with matrixes that use flowfields to calculate the values.