Nav4 SP3 bug: "Another user has changed the definition

also try to restart the server.

I think there must something be changed somewhere between 4.0 and 4.0 SP3 because I've noticed that if I add a new field, I cannot really use it until I log off and log on again to the database because I get the another user has modified the Field table error. And I don't remember it from older versions. Logging off and on again always helps so try this.

May be it is connected to some change of object cache to prevent overwriting new objects by older when recompiling the objects... #-o

marco.morreale wrote:

Alle these tables definition has not been changed.

With the newer versions ( started with some 3.X Version) it is sufficient just to look at the table design (without changing anything) for this error message to appear.

We had what was a similar problem with 4.0 SP1, except it would actually crash the client. My resolution was to absolutely make sure that everyone was out of Navision, and on my client I set the Object Cache to zero. Then I compiled all objects. Just for good measure, I even did an optimize.

In some cases, on objects that I knew were causing problems, I would save the object as a text file, then delete the object (as long as it wasn't a table), and then import that text file, compile, and that also seemed to work in some cases.

I had also gone to all clients (well my staff did) and changed the Object Cache on each client to zero as well, and deleted zup files in many cases as well.

Some combination of all of this stuff resulted in it not crashing anymore. This error is a graceful error rather than an all out crash that I was experiencing, but it sounds like it is the same thing. And that is that a client somewhere has an out of date version of an object or objects causing all types of problems.

We're getting this error too - very frustrating!

We expericenced the error with v4 and are still getting it with v4 SP2.

It doesn't seem to make any logical sense, but appears to relate to the change log in our case?

One of the palces it happens for us is on the Item Card - when an item is blocked/unblocked, there is a sequnce of checks that are carried out, as well as the user having to enter a reson for the item to be blocked. One day it'd be fine and the next it'll cause lots of problems.

Has anyone found a solution to this one at all, we've tried all the basic things so far (logout, restart, recompile, etc.)

I had the message above appearing whilst doing development in my dev environment V3.70 SQL. Initially I wrote a Codeunit to clear out any changelog setup/tables and logging. However even when I tried my processing again I recieved the error.

After reading this post I simply deleted my .zup file and then it all worked beautifully. Hopefully it is that simple for others. =D> =D> =D>

73's

Kylea
VK6FXYL

Hi

I installed Windows Vista Platform Upgrade which upgraded the finsql.exe version from 4.0.3.23305 to 4.0.3.24080 and then this error started to appear.

I tried to delete all change log setup and that did not change anything.

The server is SQL 2005 SP2 x64 bit. The error does not appear when connected to my local SQL 2005 SP2 x32 bit server nor when connected to an SQL 2000 server.