Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 295 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Deleting Production Orders
ouredp
Member Posts: 56
Hello,
This is just another post about Database compression.
As I read on other posts "Date compression on Item Ledger" seems to be a dangerous report, suppressed in 5.0 !
So let´s live with that, but... this has an influence in "deleting finished production orders".
Navision checks the existence of Item Ledger Entries on the delete trigger.
So our old prod.order stay in the DB as well !
Does anybody know waht is this check for ? Could it be removed ? With what kind of consequences ?
This is just another post about Database compression.
As I read on other posts "Date compression on Item Ledger" seems to be a dangerous report, suppressed in 5.0 !
So let´s live with that, but... this has an influence in "deleting finished production orders".
Navision checks the existence of Item Ledger Entries on the delete trigger.
IF Status IN [Status::Released,Status::Finished] THEN BEGIN
ItemLedgEntry.SETCURRENTKEY("Prod. Order No.");
ItemLedgEntry.SETRANGE("Prod. Order No.","No.");
IF ItemLedgEntry.FIND('-') THEN
ERROR(
Text000,
Status,TABLECAPTION,"No.",ItemLedgEntry.TABLECAPTION);
So our old prod.order stay in the DB as well !
Does anybody know waht is this check for ? Could it be removed ? With what kind of consequences ?
0