There is a minor problem with the MSG command in that any message issued that does not exist or is blank will not sound a beep.
This may sound trivial but this is used in some packages to force a beep and then issue warnings with Umessages based on data.
Some will probably have done this in the first place but the obvious workaround is to use UMSG(CHAR(7)).

Yep, We found that one 2 days ago.

I'm about to report it to PRO-IV support, so it will be fixed soon!!!!!!!!!!!

Rob

Thanks Rob.

We too have reported this the other day, along with the other posts I made (except the compat. issue).

By the way, this PRO-IV forum thing is great - thanks.

There is a workaround which we have just discovered...
MSG(999,' ')
{note the space between the quotes}

This works because there is a new feature with 4.6 which allows you to put '%1' into a message and assign %1 a dynamic string by calling the message like this:
MSG(1,'string')
and define message 1:
'ERROR - %1'
(works for %2, %3 etc.)

We just realised that you don't even need to have the message there to do this.
Could have been been the introduction of this new feature that took away the beep on MSG(999) in the first place!