With those modifications the Repeat window comes up quickly on a new record, and the "This event has repetitions" message comes up quickly on an event in a chain of repetitions.

This sounds like an improvement =) Thanks for trying that out!

With the If - Then stepping around the SQL search in most instances, because it is rarely needed (hence the big improvement), do we know it works when it IS needed? Should we not contrive an instance of that rare case that the search is intended to respond to?

With the IF statement in the script, we're assuming that none of your users would delete the value in the field you have mapped to the dbk_repeatingid option (usually DBk_Repeating_id) in your "Source No" layout. This field is set when repeating events are created. If it is blank, then we can assume there are no repeating events and don't need to perform the query.

Do you feel that there is a risk of your users deleting the value in this field?

No - Those fields won't be exposed to any users. Only my fat fingers get in there.

Thanks for all your help!

Thanks, wsmiii,

I verified with the team that the query would not result in any records being found unless that dbk_repeatingid field has a value, so we'll be updating our script in a future update to reflect this change.

Thanks for diving into this with us!

KC