Volker


As Matthew pointed out I was totally ignoring the fact that the word NULL was in quotes. I apologise for that. You are right in that it appears that the engine is also getting it wrong.

I suggest you log an incident for Tim.

Roy Lambert

Volker,

<< we wondered why a few of our triggers dont work anymore... (version 2.28b5 is the last working version)
we found out that:

 if standard null behavior is enabled string consts can be miss-parsed and lead to a ?internal-crash? of the engine. >>

I've fixed the issue, and will have a new build out shortly with a fix.

Tim Young
Elevate Software
www.elevatesoft.com