Committing Changes to the structure of your database and opening some of the various dialogs for fields such as field options and specify calculation lock the entire table involved--preventing any edits to data in the table. Thus, this could interfere with any script running at the time the table is locked in this fashion. Users will find that they are locked out of the table at the same time if they attempt to edit data.
This might explain why your scripts did not run as expected--especially if Set Error capture was used to suppress error dialogs.
Making structural changes to your database while others might be using it isn't really a safe thing to do. It's a bit like trying to change the fan belt on your car without turning the engine off first. Among other things, if you are so unlucky as to experience a network glitch while committing such a change to your database, you could corrupt your file, crash it and thus bring down your whole system until you can revert to a backup copy...
Thank you for posting.
As you note, this behavior has been reported, and PhilModjunk describes well the caution it calls for (thank you).
You can view other customers' posts on this issue at: Script Step Failure when developer has 'Manage Database - Specify Calculation' Dialog box open.
When you say "the entire table involved" how exactly is that defined? If I am on a layout from a table and open Manage DB can I work in that table only, or can I not do anything? I am going to test on this next week and will post the results.
If you open specify calculation for a field defined in a table called "contacts". All records in Contacts will be locked against edits until you close the dialog. Presumably, when you click OK and changes are committed to the DB, any table being updated will at that point also be locked against any edits by users or their scripts until the changes have been comitted...