Error 1355 in module 19

ams79

Hi,

I'm running a report and mbs-3.70 give me that error: Internal error 1355 in module 19.

I have a list of navision errors that tells me that: #Err_DB_DBMNotReentrant DB_Err(1355)

If you have any idea about it please help me.

Regards,

ara3n

Have you really searched this forum?

http://www.mibuso.com/forum/viewtopic.php?t=8067&highlight=1355+module

themave

In both cases, wrongly selected key or poorly structured SIFT fields and keys are most likely to be the problem

since this is a known problem, shouldn't it just be fixed by Microsoft, rather then users having to come here and ask for help, only to be told to search the forum, by other more experienced users who have seen the request for help so many times they are sick of seeing it?

Just some of my random thoughts

kriki

themave wrote:

In both cases, wrongly selected key or poorly structured SIFT fields and keys are most likely to be the problem

since this is a known problem, shouldn't it just be fixed by Microsoft, rather then users having to come here and ask for help, only to be told to search the forum, by other more experienced users who have seen the request for help so many times they are sick of seeing it?

Just some of my random thoughts

We refer to other posts to avoid that we have to write the solution 10000 times. This would make searching (and especially reading the results of a search a lot more timeconsuming).
And indeed they should fix it, but they still haven't.

themave

Sorry, don't mean to criticize you, because you (and other posters) have helped me tremendously over the years. And I apologize for complaining to the wrong people. I just have a lot of frustration with Navision at times. I first started with Navision as an end user back in 1999, and those first two years the online forums (Navision.net) helped a lot. So, much great information, but then we got a stable Navision running and didn’t really need the boards so I only checked in every few years as a new upgrades came out, but most upgrades didn’t offer much, so we had stayed with Navision 2.0 with advanced distribution. Well, now we are upgrading to 4.0, and I am finding so many of the same problems that I first experienced way back in 1999. Like this error, just got it this last week when I was renaming a item record in Navision 4.0. Imagine my frustration, 6 years, 4 major program upgrades (2.6, 3.1, 3.7, 4.0) and the same known problem still pops up.

So, keep up the great work, and I will try to be more constructive.