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
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Error handling on outmsg.getstream?
claras2005
Member Posts: 17
Hi
I am currently programming a system where I can send orders from Navision Attain 3.70 to a linux server via sockets.
I am using the Attain communication components and everything is working fine. I can send the order and get the return message from the server. So fare so good.
But because the system is going to run “automated” in a job scheduler I would like to make it a little more stable towards potential errors. So the first thing I tried was to stop the socket server. And there my problem start. I get a windows error when I do the
OutS := Outmsg.GetStream;
Call.
Are there any way to check that the socket connection is running and catch that status in C/AL code so that I can make my system more stable?
I thought I could you the win socket ocx but when I try to use it from Navision I get a message that I need to use a developer license for the ocx?? Anybody know how I get this?
I am currently programming a system where I can send orders from Navision Attain 3.70 to a linux server via sockets.
I am using the Attain communication components and everything is working fine. I can send the order and get the return message from the server. So fare so good.
But because the system is going to run “automated” in a job scheduler I would like to make it a little more stable towards potential errors. So the first thing I tried was to stop the socket server. And there my problem start. I get a windows error when I do the
OutS := Outmsg.GetStream;
Call.
Are there any way to check that the socket connection is running and catch that status in C/AL code so that I can make my system more stable?
I thought I could you the win socket ocx but when I try to use it from Navision I get a message that I need to use a developer license for the ocx?? Anybody know how I get this?
0
Comments
I created a codeunit that calls my socket logic with and if around the run.
Now I can catch that there is an error (just not the details about what the error is).
I would still like info why winsocket don't work from within C/AL if anybody knows the answer.
There is nothing in the standard Navision objects that allows you to open a continuous socket connection. We had to write our own .NET component to monitor a socket connection and 'convert' the process into something that Navision would understand (we use MSMQ for that part).
RIS Plus, LLC
MVP - Business Apps
I think that my dirty solution will do the job, else you are right then I will have to program my own dll to do the job.
Wierd that navision only make such a light implementation of a interface, I would have thought that all people need some kind of error handling in their code.
The way I see it... if you're going to expose an object, expose the entire thing. Instead, Navision esposes only parts of them, and sometimes even changes the interface as well.
RIS Plus, LLC
MVP - Business Apps