Just curious to know if anyone has had issues when going from 5.6.3 (or any flavor) to 7.6.2 ( 7.6.4 )and have a WHERE clause crash the fex. I spent days working on, playing with and even opened a case with IB, who recommended taking out and putting back to see what was occuring. Of course, I'd already done a lot of that, but did it again to see. Ended up it was the WHERE clause which was rather complex. I was able to pull one element out to a separate where and it finally worked.

Was as I said curious to know if others have had any issues.

Thanks.

We went from 5.3.3 to 7.6.2 and I must warn you that there is a lot of code tightening. Things that you were able to get away with, you can no longer do. For instance in the AYM and AYMD subroutines, it makes you use the legacy date formats as they are documented. YYMD no longer works.

As for WHERE clauses, the only one that caused a problem was a date screen against a SAS ODBC source but that was a bug for which I received a fix and I got an error message, not a crash.

Sorry.

Similar issue experienced:

Works in v5.x fails in v7.6.x
------------------------------
NEW_FIELD/D20.5 = IF FLAG EQ 0 OR MISSING THEN 0 ELSE VALUE;


Now needs to be:
----------------
NEW_FIELD/D20.5 = IF FLAG EQ 0 THEN 0 ELSE
IF FLAG EQ MISSING THEN 0 ELSE VALUE;

Code tightening I suspect...

P

We experienced issues very similar to PTP with complex WHEREs and IF-THEN-ELSE in DEFINEs - especially where "MISSING" was concerned. And that was just moving to 7.1.x from 5.3.6. I would suspect even more tightening moving to the 7.6.x world

Yes Leah - there is a lot of code Tightening...and you can't get away with what you used to do. We had several 'New to WebFocus' people..and they had done some strange things..that no longer worked. Us old Focus people...were surprised it got thru in the first place...
So be prepared with complex Where's, if than elses and MISSING.

NEW_FIELD/D20.5 = IF FLAG EQ 0 OR FLAG EQ MISSING THEN 0 ELSE VALUE;