FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.


Dec 15, 2016, 4:57 PM
82 Posts

Proceed with caution and no guarantees ...

  • Category: Domino Designer
  • Platform: Windows
  • Release: 9.0.1
  • Role: Developer
  • Tags: onchange
  • Replies: 2
Corruption is nasty and many times you cannot recover from it.  If you already looked at something like this:

http://lotusibm.com/database-corruption-and-troubleshooting/

and it has not helped.  And you've already got a backup of the app in case you break something else.  Copy the problem form into a brand new db,  Open that db in designer.  Right click on the corrupt form in the Forms list in the database bookmark panel (ie, on the far left where you see all the db elements) and from the context menu choose 'Edit with DXL' (the prompt that says 'Editing DXL of design element can cause loss of information' is not lying).  When the Form opens click the Source tab towards the bottom (you will see a Design tab and a Source tab).  You will see things like:

field type='text' kind='editable' name='z'><code event='onchange'><lotusscript
>Sub Onchange(Source As Field)
        Print "bob"
End Sub
</lotusscript></code></field>

and/or

<field type='text' kind='editable' name='a'><code event='onChange'
 for='client'><javascript>alert('test')</javascript></code></field>

The Edit menu at the top has a Find/Replace selection that just might be your friend.  Good luck!

FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.