# ALERT vs prop:alrt

**URL:** <https://clarionhub.com/t/alert-vs-prop-alrt/8121>\
**Category:** questions\
**Tags:** templates\
**Created:** [April 24, 2025, 12:30pm UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121 "2025-04-24T12:30:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bjarne\_Havnen](https://clarionhub.com/user_avatar/clarionhub.com/bjarne_havnen/32/1350_2.png) [@Bjarne\_Havnen](https://clarionhub.com/u/Bjarne_Havnen)\
**Post date:** [April 24, 2025, 12:30pm UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121/1 "2025-04-24T12:30:20Z")

</div>

I have a template that opens webhelp for procedures.  
Today I discovered that if I had two procedures , browse + form, that each had the same ALERT  
statement, the second statement deactivated the first.  
Help says ALERT should work for the currently active window, but apparently, it overrwrites the scope? Is this supposed to be?

I used 0{Prop:Alrt,255}=MyHelpCode to work around it.

Using Clarion 10.

---

<div class="post-metadata">

**Author:** ![JonW](https://clarionhub.com/user_avatar/clarionhub.com/jonw/32/1344_2.png) [@JonW](https://clarionhub.com/u/JonW)\
**Post date:** [April 24, 2025, 12:53pm UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121/2 "2025-04-24T12:53:33Z")

</div>

Is it maybe just where you placed the code? Like in the form, if you had the ALERT before opening the form window, I think it would act on the current window, which would be the browse window?

---

<div class="post-metadata">

**Author:** ![Bjarne\_Havnen](https://clarionhub.com/user_avatar/clarionhub.com/bjarne_havnen/32/1350_2.png) [@Bjarne\_Havnen](https://clarionhub.com/u/Bjarne_Havnen)\
**Post date:** [April 24, 2025, 8:19pm UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121/3 "2025-04-24T20:19:10Z")

</div>

Unfortunately, no. The code is placed after opening window, right before the call to SetAlerts. Event if I had misplaced it, it should work in the first procedure, but that is where it stops working after returning from the form.  
I am not able to reproduce in a minimal application, so it is probably something else disturbing it.

---

<div class="post-metadata">

**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\
**Post date:** [April 24, 2025, 8:41pm UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121/4 "2025-04-24T20:41:05Z")

</div>

Do you also have a PROP:Alrt on a FEQ that you might have selected after returning from the form? Maybe there’s some competition there?

---

<div class="post-metadata">

**Author:** ![Bjarne\_Havnen](https://clarionhub.com/user_avatar/clarionhub.com/bjarne_havnen/32/1350_2.png) [@Bjarne\_Havnen](https://clarionhub.com/u/Bjarne_Havnen)\
**Post date:** [April 28, 2025, 10:40am UTC](https://clarionhub.com/t/alert-vs-prop-alrt/8121/5 "2025-04-28T10:40:25Z")

</div>

I found it  
The most likely reason was an emtpy ALERT() somewhere.  
I have a lot of 3rdParty accessoiries in the application, my own included, and it was my own, old listboxformatter that had an empty ALERT when killed.  
Found it searching with Notepad++