Thank you for fixing Param handed IN to trigger debug, BUT

KiwiJem · Post by **KiwiJem** » Tue 12 May 2009 05:16

Thank you for fixing Param handed IN to trigger debug, BUT you cannot SET a value to a NEW.xxx column in a before update trigger, and debug it. It is an unknown variable. and it causes the usual lockup after that as described elsewhere.

I have not tried all permutations and combinations of NEW. and OLD. in all types of trigger for reasons of time... but I suspect it is not the only one that does not recognise SETting NEW and OLD column syntax.

Elias · Post by **Elias** » Tue 12 May 2009 11:48

Do you mean that a trigger containing the

Code: Select all

SET  NEW.column_name

cannot be compiled for debugging? We have fixed this bug long long ago. Please try current build.

The functionality of viewing NEW.column expression in the watches window is added to the next version backlog.

KiwiJem · Post by **KiwiJem** » Tue 12 May 2009 22:29

Apologies, not clear enough.
you can COMPILE it, very happily, but it flags an error when you debug it - i.e. single step it.

I am using 5.5.275. Is that the latest?

I am unable to find out from the Devart site what the latest is, and there is no "check for newer versions" in the help menus.

Thanks

KiwiJem · Post by **KiwiJem** » Wed 13 May 2009 02:01

Aha, new version just released. Will download and try it. Thanks

Elias · Post by **Elias** » Wed 13 May 2009 07:59

If the problem is still reproduced please send us some sample