Hi John;

  Does your App's DW Control try to handle / help the App user out of this predicament with PowerScript code in the ItemError event?

Regards ... Chris 

I concur: Handle any error in the ItemError event.

However, some basic pre-validation would not be out of place. For example. if the field requires a decimal value you could check the pasted data to ensure that it is NUMERIC and contains no spaces after a TRIM(<value>) is performed.


Meanwhile, a very quick and TEMPORARY work around is:

1. create an instance variable:    BOOLEAN  ib_error_already_displayed

2. in the ItemError event:

IF (NOT ib_error_already_displayed) THEN

    // display the error message

    ib_error_already_displayed = TRUE

END IF

3. In the ItemFocusChanged event and in the pfc_save event (if you are using it) clear the flag:  ib_error_already_displayed = FALSE.
    Your particular case might require the flag be cleared in another event or two; it depends on the window & the DW.


That will stop the annoying 50 instances of the error msg in its tracks.

i have a 'paste' object and send the pasting string and reference to the datawindow instead of using just the standard PB or windows paste function.

first step is to change the paste string into an array of strings to handle multi column/row pastes

From there strip out spaces, remove tabs, remove CR/LF (for multi row paste) and handle moving/adding rows if it is a multi row paste. (note, if there is ONLY a space as the pasted value, it is likely they want a space so you may want to keep it rather than replace with empty string)

use the send function to send a tab to the datawindow to move to the next column

Use setcolumn and settext and accepttext to allow the datawindow logic to run for itemchanged events.