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
- 301 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
OLE DB Provider error on reading from a linked object nav table
Mikel
Member Posts: 1
Hi Everybody!
I had an error on Dynamics NAV 2016 Windows Client when managing a linked object table (wich is a SQL view) from C/AL. These means that everything is fine when I run the object table from development evironment but when I use this object from C/AL (only making a findset) it chrashes with "The operation could not be performed beacuse OLE DB provider "SQLNCLI11" for linked server "DatabaseName" was unable to begin transaction.
The funny thing is that this have worked in NAV 2009 with the same C/AL Code. Has anything changed about this? Any tips?
Thanks!
I had an error on Dynamics NAV 2016 Windows Client when managing a linked object table (wich is a SQL view) from C/AL. These means that everything is fine when I run the object table from development evironment but when I use this object from C/AL (only making a findset) it chrashes with "The operation could not be performed beacuse OLE DB provider "SQLNCLI11" for linked server "DatabaseName" was unable to begin transaction.
The funny thing is that this have worked in NAV 2009 with the same C/AL Code. Has anything changed about this? Any tips?
Thanks!
0
Comments