Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
TIP: Using a 3.70 client while programming a 3.60 database
eromein
Member Posts: 589
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.
(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."
If it was hard to write, it should be hard to understand."
0
Comments
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.
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]
If it was hard to write, it should be hard to understand."
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!