Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Communication Component version 2 and Socket Bus adapter
MortenKS
Member Posts: 7
I have a question concerning the Navision Communication Component version 2 as well as the Navision Socket Bus Adapter.
I am using both the above mentioned automation objects in a solution for Navision Attain 3.01 B. The solution now has to be updated to a Navision 2009 R2 or Navision 13. So the question is if the before mentioned automation objects does work in any of these two versions? And if so is there a limitation when comes to 32 vs. 64 bit operating system? Or client type classic vs. RTC.
If none of the automation objects work in any of the versions the alternative in my view would be to code a C# dll. and handle the socket communication by myself.
If anyone know about this please feel free to reply.
Thanks in advance.
I am using both the above mentioned automation objects in a solution for Navision Attain 3.01 B. The solution now has to be updated to a Navision 2009 R2 or Navision 13. So the question is if the before mentioned automation objects does work in any of these two versions? And if so is there a limitation when comes to 32 vs. 64 bit operating system? Or client type classic vs. RTC.
If none of the automation objects work in any of the versions the alternative in my view would be to code a C# dll. and handle the socket communication by myself.
If anyone know about this please feel free to reply.
Thanks in advance.
0