Problems after Navision Financial 2.60B moved to SQL Server

DRB
Member Posts: 105
Hello,
I have recently migrated a Navision Financial 2.60B database to SQL Server 200 SP3 with 2.60C executables, navision objects are not changed. Now while posting Cash Receipt Journal etc. system gives error related to inconsistency, whereas same task is being done on native.
If any of you know its reason, then please share it.
While in 4.x onwards version, when editing a codeunit, we might get error that you don't have permission to edit code but in this version system gives error that you don't have permission to write in Table x etc. Any ideas on this?
I have recently migrated a Navision Financial 2.60B database to SQL Server 200 SP3 with 2.60C executables, navision objects are not changed. Now while posting Cash Receipt Journal etc. system gives error related to inconsistency, whereas same task is being done on native.
If any of you know its reason, then please share it.
While in 4.x onwards version, when editing a codeunit, we might get error that you don't have permission to edit code but in this version system gives error that you don't have permission to write in Table x etc. Any ideas on this?
-Dhan Raj Bansal
Linkedin Profile: http://in.linkedin.com/in/dhanrajbansal
Linkedin Profile: http://in.linkedin.com/in/dhanrajbansal
0
Comments
-
It looks like problems with rounding...
The permissions: aren't you editing some codeunit with indirect permissions to protected tables and you are using wrong license whcih have no write access to this table? Like editing CU 80 with application builder license and not solution developer?0 -
kine wrote:It looks like problems with rounding...
Seems that is the reason, but how to solve it?
Regarding license: It is a developer license which works properly on version 4.x onwards, but not working well on NF 2.60C, can this be the case?-Dhan Raj Bansal
Linkedin Profile: http://in.linkedin.com/in/dhanrajbansal0 -
Solution depends on real source of the problem... and to know the source, you need to find why there is the inconsistency...
Regarding permissions: some versions of NAV used on SQL had problem that even when NAV wanted to read from empty table, you needed to have permissions for this table. It means, iven the module was not "activated" (no setup etc.) you needed to have permissions for NAV to check that there is no record to read (native DB had no problem with this...)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