TIP: Using a 3.70 client while programming a 3.60 database

eromein
eromein Member Posts: 589
edited 2008-01-30 in NAV Tips & Tricks
Hi,

(This was already posted on the wrong forum; this should be the right place.)

I'm using the 3.70 for programming course of the great new features. But here is the problem.

When programming in a 3.60 database, which will be used in combination with 3.60 clients, problems will occur if you compile objects (with your 3.70 client) that uses ocx components.

You can see it if you compile codeunit 423 Change log management with a 3.70 client. Open de database with a 3.60 again and try to (for expample) create a new sales order.

Hope this post makes any sence, and you will have gained some usefull knowlegde.
"Real programmers don't comment their code.
If it was hard to write, it should be hard to understand."

Comments

  • Timo_Lässer
    Timo_Lässer Member Posts: 481
    Hi!

    I'm using 3.70 client for 3.60 database programming, too.
    There are only differences with the handling of RecordRef, FieldRef, ...
    You can solve the problem, if you compile these objects with a 3.60 client.
    Timo Lässer
    Microsoft Dynamics NAV Developer since 1997
    MSDynamics.de - German Microsoft Dynamics Community - member of [clip]
  • eromein
    eromein Member Posts: 589
    I tried that, didn't work. I had to manualy change the automation server to the old values. And trust me, it's a lot!
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • kriki
    kriki Member, Moderator Posts: 9,121
    eromein wrote:
    (This was already posted on the wrong forum; this should be the right place.)
    After 5 years, I found out this post, so I locked the old one and it will be deleted later, just to clean a little bit.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

Categories