Navision 2.6E and 4.0SP1 using same SQL Server 2000
davmac1
Member Posts: 1,283
Does anyone know if there is a problem using the new xp_ndo.dll (from 4.0SP1) extended stored procedure with 2.6E?
Plan to have Navision itself installed on different Windows Servers with all users running remote desktop, so the only common point is the extended stored procedure in the Master database
Plan to have Navision itself installed on different Windows Servers with all users running remote desktop, so the only common point is the extended stored procedure in the Master database
David Machanick
http://mibuso.com/blogs/davidmachanick/
http://mibuso.com/blogs/davidmachanick/
0
Comments
-
If you use database logins there shouldn't be a problem, I have multiple versions of Navision running in my SQL Server (although 2.6 is not one of them). There may be issues if you want to use windows logins.0
-
On 2.6 we use Windows logins. On 4.0 we could use database logins until we retire the 2.6 version.
So what you are saying is 2.6 would not work with the new extended store procedure?
And that 4.0 will work with the old if we only use database logins?David Machanick
http://mibuso.com/blogs/davidmachanick/0 -
I also have SQL 2K and I have from 2.6 to 4.0SP1 on it. In general I use DB-logins for all of them. But my Windows login is enabled for all of them and now I just tried to enter with Windows login in 2.6,4.0,4.0SP1.DenSter wrote:If you use database logins there shouldn't be a problem, I have multiple versions of Navision running in my SQL Server (although 2.6 is not one of them). There may be issues if you want to use windows logins.
WORKS JUST FINE!
BTW:the version of xp_ndo.dll I use is the one from 4.0SP1 (file version=4.0.1.21666).Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Alain, would you do this on a production system? On a test system maybe, but for production I would leave this alone.0
-
On a production system only if the customer upgraded from 2.60 to 4.0 and wants his old data still available for comparison or if the 2.60 is not critical.DenSter wrote:Alain, would you do this on a production system? On a test system maybe, but for production I would leave this alone.
So, indeed surest thing is (like davmac1 said) using DB-logins on 2.60 until the retirement of it.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Just received a reply from Navision support - the 4.0SP1 dll will work for both.
The documentation that comes with the distribution did not get updated and it still refers only to xp_ndo_enumusersids.
I had seen a warning in 3.70 documentation, which is why I am being ultra-cautious.
Thanks for the responses.David Machanick
http://mibuso.com/blogs/davidmachanick/0 -
Updated the dll yesterday and setup a Navision 4 database on the same SQL Server.
No problems so far.David Machanick
http://mibuso.com/blogs/davidmachanick/0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 328 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
