Problem using linked servers and views

dlebech
Member Posts: 7
Hi,
I have made a view "my_view" from a SQL Server 2000 to a SQL Server 2005 (both Windows 2003 Server) using linked servers. A Navision 3.7 client is running on the 2000 server and I use the LinkedObject property on a new table called "my_view" of course to access the view (The LinkedInTransaction is of course disabled as it should be). This works fine when retrieving data but when I want to modify a record, I get an error message:
Statement(s) could not be prepared
Incorrect syntax near 'UPDLOCK'. If this is intended as a part of a table hint, a WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax.
I have now tried different solutions and it actually works when I make the view from another SQL 2005 Server and run this through a Navision 4.0 SP3 client (still using linked servers). But I need to access the view from the 3.7 client. Has anyone else experienced this problem and succesfully solved it? My guess is that it is a problem when connecting a SQL 2000 with a SQL 2005 and in this case, there isn't much to do :-k
Any inputs?
Best regards
David Lebech
Navi Partner
I have made a view "my_view" from a SQL Server 2000 to a SQL Server 2005 (both Windows 2003 Server) using linked servers. A Navision 3.7 client is running on the 2000 server and I use the LinkedObject property on a new table called "my_view" of course to access the view (The LinkedInTransaction is of course disabled as it should be). This works fine when retrieving data but when I want to modify a record, I get an error message:
Statement(s) could not be prepared
Incorrect syntax near 'UPDLOCK'. If this is intended as a part of a table hint, a WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax.
I have now tried different solutions and it actually works when I make the view from another SQL 2005 Server and run this through a Navision 4.0 SP3 client (still using linked servers). But I need to access the view from the 3.7 client. Has anyone else experienced this problem and succesfully solved it? My guess is that it is a problem when connecting a SQL 2000 with a SQL 2005 and in this case, there isn't much to do :-k
Any inputs?
Best regards
David Lebech
Navi Partner
0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions