Std v6 table (T5107) crashes classic SQL client on compile?

vytjak
vytjak Member Posts: 36
edited 2009-10-15 in NAV Three Tier
Hello everyone,

I'm having some troubles modifying a standard v6.00 table T5107 "Sales Header Archive" - it crashes the client on compile/update. It doesn't crash when I update it on a native v6 DB opened directly with a v6 classic client, but it still crashes the SQL client when I try to import the modified object. I have also tried importing into a v5 DB - v5 native and SQL clients crashed on compile as well. Could someone confirm this behaviour? I'm not sure if this is caused by some weird corruption to the table on my DB, or my setup, or something else.

I'm working on a standard NAV2009(v6) DB, SQL 2005 Express SP2, using Nav v6 Classic client for SQL.
Vytenis Jakas
B3 Technologies - Making Technology Serve the People

Comments

  • ara3n
    ara3n Member Posts: 9,258
    is this 2009 W1 version or a localized version?
    Have you done any modification to it?
    I would try and e xport it as text and try to import it.
    I would guess it might be related to a caption or source expression being too long.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • vytjak
    vytjak Member Posts: 36
    Hello Rashed,

    the object version is NAVW16.00 (W1), although it's from a NAV2009 GB database.

    Well, I did try to do a modification on it, that's when I got a crash. After that I started looking for a reason why it crashed and discovered that it crashes my client when trying to compile a standard object (no mods) as well.

    Tried exporting as text and importing - imports, still crashes the client when trying to compile. While testing I did find out that when importing the object as a fob, it did import, and only then crashed (i.e. the object was updated when I restarted the client and opened the DB).
    The field captions look OK (all withing 30 chars), at first glance it doesn't appear that there are any other properties that would have extremely long source texts.

    I guess I'll have to start comparing it to v5.0 to find out what is the actual change that causes the crash (if it is the v6 object version that's causing it, and not something else).
    Vytenis Jakas
    B3 Technologies - Making Technology Serve the People
  • ara3n
    ara3n Member Posts: 9,258
    It could be also that NAV is crashing because of translating the table to C sharp code.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • GoMaD
    GoMaD Member Posts: 313
    Is there a solution for this problem?
    Has this issue been passed to Microsoft?
    ...
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!
  • GoMaD
    GoMaD Member Posts: 313
    i've deleted the "good old" zup file (client side), restarted the navision service (middle tier) and now I can compile the tables again from the Object Designer!
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!

Categories