Debugger wouldn't start

[Walter Vaughan]

Here's one to file away...

Have a report that builds information from a single record, and gets chosen via
a self-indexed lookup passed via -r flag. Been working for years.

Stops.

Okay. Just run it in the debugger. Attach a -db to the command line and see what
could be causing this. Except it never entered debugger. What? Back to command
line in nano-seconds. Moved the -db flag all round the command line. Made no
difference (it shouldn't).
Okay, strip the command line down to just the -f table... debugger works.
That's weird. The -V table is just 8 lines of the most simple code that I use
everywhere. Recompile it. Still no debug.

Huh?

I popped into the fpChatRoom, and got advice I expected. It then was staring me
in the face. I did not rebuild the index the self-index table used. While Tony
and JE are racking their brains with the usual suspect of maladies, I just
rebuilt the index.

Bingo. Now it entered the debugger fine with the whole command line intact, and
runs the report just fine.

So, while I expect that a damaged index to cause a failure with a report, I did
not expect it to not work in the debugger. However I'll concede that the failure
to enter debug mode would be expected if the index would not work with the
processing table.

So the behavior is correct, I am just passing on a tip that the failure to enter
a debug mode on a table *CAN* be caused by a bad index.

And a thanks to Tony and JE for making me look around the corner for the solution.

--
Walter