So where should compound statement be inserted in the samples I posted this week to get the code work right? Have a look below. But first … … code can work technically right when it compiles and doesn’t throw any run-time error, which is a minimum of any code IMHO….
Have a look at these code samples and tell me where a compound statement, i.e. BEGIN-END, should be constructed to get the code work right. Just dare without going into NAV and verify. [8-|] Sample 1 1. SalesCommentLine.SETRANGE(“Document Type”,SalesQHeader.”Document Type”);2. SalesCommentLine.SETRANGE(“No.”,SalesQHeader.”No.”);3. WHILE SalesCommentLine.FIND(‘-‘) DO4. SalesCommentLine.DELETE;5. SalesCommentLine.”Document Type” := SalesOrderHeader.”Document Type”;6. SalesCommentLine.”No.” := SalesOrderHeader.”No.”;7. …
This last item in my NAV2013 Beta to RTM – Some Striking Code Changes series is addressing code changes NAV core team made to get IF-THEN-ELSE statements coding standards compliant. If you read the Microsoft Dynamics NAV 2009 Developer and IT Pro Documentation on IF-THEN-ELSE, and also on the use of…