The only situations I've seen where code truly spirals off into nowhere, were due to a server upgrade gone wrong: the server booted, but was still running with DLLs from an earlier version. It runs -- you really don't want it to run!

For the debugger line mismatches, I've seen two sources:

1. Sharps (#) and colons (:) in your executable code. If an executable line contains a sharp or a colon, for some reason the debugger gets its lines mismatched. I've seen it occur in select case statements when the statement spans multiple lines. Nowadays I just try to omit it.

2. Less clear how & why, but blank lines outside of subprocedures/functions/properties/methods also cause mismatches.

As for the oddity executing the code, assume you've resolved the debugger line mismatches. What's the last line that was clearly checked properly, followed by any branches it may cause, and any preceding code that sets the values used on the line? I know, clear as mud.

Essentially, I'd need to see how the "trigger line"s data was retrieved; and then where that line might've jumped to execute later in the code.

Thanks Mike for your reply,

I will try today to cancel out the effects of sharps "#" , colons ":" and blank lines  on the debuggers behaviour. Hope it will help.

But what causes me headache is that the execution was also wrong  - the skipped 'Select Case'  block is a hefty show killer.

I meanwhile have replaced all 'Select case' statement against 'If then else if else endif' blocks without success.

Will keep you informed.

TIA, Joe

Hi,

after further testing I could solve the worst part of the problem - the execution of the Lotusscript code is in fact correct. Due to the fact that the debugger is showing wrong code I myself have created a mistake in the process of getting more insight into the debugger problem, which has lead to a code where an entire "Select case" block was not executed because a variables value was meanwhile set to a wrong value.  That's the good news !

The bad news are the fact that the debugger still starts to become confused in one library and one method  ( meanwhile changed the Set property into a sub - also no success ) It starts with displaying one line behind and then escalates.

Am still in the process of removing in all design objects concerned the '#' & ':' chars & the blank lines between methods that Mike suggested. Still hope this will solve it.

Joe

. The debugger loses sync whenever this certain method in this one specific class is called. Other class methods do not have this effect. Renaming the method or changing the type (Property Set -> Sub) did not help. The library where the class resides is of medium size (~ 40k) and contains another 3 public classes and 2 private classes, which do not suffer from debuger antipathy, if not called from within the problem class.  Can't see anything special which could explain this problem.

Joe

Hi all,

I finally found the problem why the debugger showed the wrong source code in 1 of my libraries.

As define in basic and in Lotusscript as well, it is allowed and valid to write 2 staments separated by a colon.

But this was what throws the debugger out of sync.

The below listed  code was one of 2 code blocks which caused the problem. For each line containing a colon the debugger went wrong one line.

Because I had 2 "Select Case" blocks at different locations in that library, the number of lines the debugger went wrong was dependend on the location relativ to these two code blocks. Behind the 2 blocks it was the max.

Thus Mike Woolsey was right in what he wrote. But I simply have not seen these two code blocks and the colons there. Detected it now by chance ...

Select Case Left$(s$,3)
            Case "INF"
                me.z_stat="Info": me.z_msglvl=0
            Case "WAR"
                me.z_stat="WARNING": me.z_msglvl=1
            Case "ERR"
                me.z_stat="ERROR":  me.z_msglvl=2
            Case "DEB"
                me.z_stat="DEBUG": Me.z_msglvl=9
            Case "FAT"
                me.z_stat="FATAL": me.z_msglvl=3
            Case Else
                me.z_stat=s$: Me.z_msglvl=0
        End Select

So this is a bug of the debugger, as the colon is a valid syntactic element of Basic and Lotus Script.

But honestly said,I think instead of fixing the debugger IBM/HCL should exclude the colon in the next version of Lotusscript and raise an error if used.

Joe