Hello To All,
Thanks for the input. I feel better knowing that it’s not something stupid that I’m doing.
Gary, I will use the “message” method you suggested. I actually have often used the message method myself, but the single-step method always shows the value of the current variable at the bottom of the procedure window anyway, so there usually is no need for a message statement so long as the debug statement properly stops the macro before continuing. But if this a method you use, it will be a good one.
For most code commands, pausing the macro at individual steps is usually not very important. Grouping, or sorting, etc. is straightforward, and never poses a problem.
The need for interrupting a macro is really needed when complex changes are being made to the database, such as when a new record is being added, or changes to a new or an existing record are being made. In these cases, you better make darn sure the macro is doing what you want it to do, and nothing else! Closing a sold stock record, for example, or splitting a stock record into 2 records because of a partial sale, or editing a compound’s property or thermodynamic property, etc., etc.
And especially when a calculated variable is used to change the value of a “DummyNumber” field in the database with a formulafill. That field’s total value may be used to converge on an iterative solution to a polynomial equation. Unless you can reliably stop the macro to look at the temporary values in the field and its total, it’s darn hard to know whether your iteration technique is converging or not, or to decipher WHY it’s not converging.
These all require each individual macro step to be examined, to see what possible problems might arise in some future run. Debugging a procedure (AS WE ALL KNOW) can be fraught with unknown problems, and it’s essential to carefully examine each step to see what might cause errors in the future. “Current results are no guarantee of future performance”, and all that.
But, the suggestions you all made here will be useful. I hope that eventually Jim will uncover the reason for the single-step problem, and will come up with a fix. He’s got a lot on his plate, and we shouldn’t be pressing him. He is making good progress.