Seems like you're using Mathcad 15, which is good because in Prime it's not possible to do:
Which you obtain by pressing [CTRL-ENTER] instead of +.
Note that you can only break an expression at a summation point.
Success!
Luc
As a crude workaround you may insert "program" lines consisting of empty strings ( -> "" ) when a program runs over a page break to avoid your program gets unreadable.
The only way to insert a linebreak which Mathcad offers is when entering a long sum via "Ctrl" and "Enter"
This will not work with your chain of logical expression. You will have to use abbreviations as workaround.
Something like
bool1 <-- IsOK(a,b) AND IsOK(c,d)
bool2 <-- IsOK(e,f) AND IsOK(g,h)
"OK" if bool1 AND bool2
"NOK" otherwise
In your special case I would not use and call IsOK in the IsOK_all routine at all. And you may use simple argument names in IsOK_all rather than using the names you intend to call this function later. Like you used "ist" and "soll" in IsOK.
WE
Here is another option:
You would replace the numbers with your actual checks. For example, change 1<2 to IsOK(dm,am)="OK"
Unfortunately, with the exception of the addition operator, you can't automatically break lines in Mathcad 15 (and below).
There are several methods of getting round the problem, which usually take up more vertical space (I assume that's less of a problem?).
The first thing you can try is reducing the size of your standard font - that may squeeze a few expressions into the page,
The second thing (which I assume you've either done or don't want) is to use Landscape mode.
Then you enter the realm of modifying your expressions to use less horizontal room. For example, ..
- Put your function arguments into a vector and either re-assign to the variables within the function or modify your function to pick the appropriate elements from the vector.
- Break up long expressions manually and piece them back together again on separate lines.
See this image for some examples:
Stuart
You're wasting a lot of space with your IsOK function.
Using it every time and checking if the output is equal to the string "OK" or "NOK" wastes more.
Why not have the function produce a logic TRUE or FALSE automatically by defining it as:
Then you can just test:
But even that takes more (horizontal) space than the simple and clear:
Success!
Luc
And also you could turn your evaluation method around, in returning when a condition is NOT met. So instead of:
You do:
Success!
Luc
Odd number year maybe because i use the SHG 2 times
condition:
ISOK(SHG;Sfg1.g)
ISOK(SHG;Sng2.5)
Right counted but its that what i need to 
