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
- 310 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
report.RUN vs. report.RUNMODAL
pbatink
Member Posts: 3
Hello everybody,
In standard Navision report.RUN is used to print documents while posting.
Is this a correct statement?
Some report.RUNMODAL statements were added by our former NSC to also print documents while posting from codeunit 82.
We experience deadlocks that might be caused by report.RUNMODAL waiting for the printer to return control to Navision.
Can anyone explain the different approach?
Kind Regards,
Peter.
In standard Navision report.RUN is used to print documents while posting.
Is this a correct statement?
Some report.RUNMODAL statements were added by our former NSC to also print documents while posting from codeunit 82.
We experience deadlocks that might be caused by report.RUNMODAL waiting for the printer to return control to Navision.
Can anyone explain the different approach?
Kind Regards,
Peter.
0
Comments
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
I'm aware of the technical difference between RUN and RUNMODAL.
No, there is no navision error involved but a SQL deadlock message.
What keeps me busy is: what happens when the windows printdialog window is visible for quite some time and the booking process doesn't continue? Are there still tables locked or does the printing take place after a COMMIT?