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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
You cannot make any changes in the database from this tr...
Magno
Member Posts: 168
Hi,
I use an application server and i always get this message:
But i use
Normally, if any errors occur in that codeunit, the NAS will get in the then but not stop to run. apparently here it does throw the error.
Now, i looked through the code with client monitor(code is 2 complex to debug) and i can say for sure we only call tables and codeunits in the NAS.
Can anyone tell me from which triggers this error could come, or how this could be?
I use an application server and i always get this message:
You cannot make any changes in the database from this trigger.
But i use
if not cuTemp.run() then
Message('Error in codeunit');
Normally, if any errors occur in that codeunit, the NAS will get in the then but not stop to run. apparently here it does throw the error.
Now, i looked through the code with client monitor(code is 2 complex to debug) and i can say for sure we only call tables and codeunits in the NAS.
Can anyone tell me from which triggers this error could come, or how this could be?
0
Comments
C/Front can throw that error message if a db modification (insert, modify or delete) is attempted before beginning a write transaction...
(Seems a silly comment, I know -- why call 'incorrect' C/Front code when you are inside C/AL code already -- but, then again, maybe you are doing some sort of cross-database replication or some such..)
:-k