NAV in debug mode: why code changes are not transferred?

Nosta
Nosta Member Posts: 31
edited 2009-08-14 in NAV/Navision Classic Client
Hi all,

I faced with strange behaviour of NAV when I run it in debug-mode: code changes, I've made in NAV objects are not tranferred to NAV debugger and system ignores my changes when I run my objects after compiling and saving them. I turn off and close debugger, run objects in simple run-time mode: NAV does not see any chanes I've done just few seconds ago :shock:! It concerns the changes in CAL code only. Everytime, to see how new code works, I need to restart NAV.
this problem came up last week on NAV 4.3 (build 23305), but no changes in the system environment were done during last month.

Can you recommend me how to solve this issue?

Answers

  • generic
    generic Member Posts: 511
    Get the latest executables. The debugger in Nav is buggy.

    If it solves your issue then great. If not then you are out of luck.
    You can try to run develop on finsql.exe/fin.exe


    The classic client development rightnow is on support mod. So nothing will be fixed until they kill it.
  • garak
    garak Member Posts: 3,263
    did you set you objectcache to 0 (zero) ?
    Do you make it right, it works too!
  • Slawek_Guzek
    Slawek_Guzek Member Posts: 1,690
    Perhaps you're debugging a codeunit with SingleInstance property set to yes ?
    Slawek Guzek
    Dynamics NAV, MS SQL Server, Wherescape RED;
    PRINCE2 Practitioner - License GR657010572SG
    GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
  • kapamarou
    kapamarou Member Posts: 1,152
    Please let us know exactly what you are doing. This may happen if you launch a form from a form, for instance, design that newly opened form and then rerun the procedure without closing the original form. In that case the client may end up using the object from the "Object Cache" instead of reloading.

    I think I still get this with a client that is on 3.70 whenever I change the menu forms...
  • ara3n
    ara3n Member Posts: 9,258
    if you are using a single instance codeunit, the only way to get the changes is to login and out.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Nosta
    Nosta Member Posts: 31
    Slawek, ara3n: yes, this happens on singleinstance codeunit. So, it's known issue and I have to login and out every time when I want debug my changes in this COD. Am I right?
  • garak
    garak Member Posts: 3,263
    Yes, if u use a SingleInstance CU, the Client loads this CU in his memory and work from there with him.
    So, if you make some changes in this SingleInstance CU, u must logoff (to clear the allocation) and login to work with the changes. This is not a bug.
    Do you make it right, it works too!
  • Nosta
    Nosta Member Posts: 31
    I've been working for years with NAV but have never faced with this problem before :) many thanks!
  • garak
    garak Member Posts: 3,263
    Please and you're welcome
    Do you make it right, it works too!
  • David_Singleton
    David_Singleton Member Posts: 5,479
    8><
    David Singleton
  • Belias
    Belias Member Posts: 2,998
    I've had the same issue a pair of times, but with NO singleinstances if i remember well...unfortunately my memory is a bit foggy about this, as the last time happened some months ago... :-k
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog

Categories