I'd seen a few databases whose previous customization consultants from different VARs use
IF Rec.GET(x) THEN;
Is this a coding convention for C/SIDE?
Why not just Rec.GET(x); or IF NOT Rec.GET(x) THEN ERROR(errormsg);?
The reason for asking is this would not have been a good coding practice elsewhere.
NAV - Norton Anti Virus
ERP Consultant (not just Navision) & Navision challenger
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
But if I use it I make sure the record is cleared just before it. Something like this:
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
ERP Consultant (not just Navision) & Navision challenger
Personally I don't like the IF MyRec.GET THEN; construction, to me it lacks proper design attention. To me when you start using an IF statement, you have to think about actions to take for both the TRUE and FALSE legs.
On the other hand, I've used it from time to time to quicky go around an error message. When in a time crunch you don't always have the luxury to sit and think things through. As long as the code properly handles the situation it's just a means to an end really. Not very elegant, but if it works, it works.
RIS Plus, LLC
MVP - Business Apps