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
- 264 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
OCX working on classic and crashes on RTC
Pomaroli
Member Posts: 37
Hello,
we are migrating from 3.7 to nav 2009 and we have an OCX which isn't working on RTC but on classic all workine fine.
the failure which is shown when calling the ocx the first time in RTC is "this process is not supported".
can we debug the call to see which process isnt supported or should we consider a redesign of the ocx ?
the ocx is an wrapper of some dynmic libraries.
thanks
we are migrating from 3.7 to nav 2009 and we have an OCX which isn't working on RTC but on classic all workine fine.
the failure which is shown when calling the ocx the first time in RTC is "this process is not supported".
can we debug the call to see which process isnt supported or should we consider a redesign of the ocx ?
the ocx is an wrapper of some dynmic libraries.
thanks
0
Comments
Have you read this excellent article?
http://msdn.microsoft.com/en-us/library/ee909565.aspx
thanks yes i've already read this article which helped understand that the ocx runing only on the RTC Client, the ocx is of type :
"Automation objects with a user interface, such as OCX types"
it seems to me that we not come out of NAV with the call, the ocx test functions are not arrived before error message.