Hi @DeepshipEngineering. No. The "default.ivb" looks like the name of the file where the default Inventor application level VBA project is stored. The code example above is in iLogic (or vb.net), instead of VBA, but it could easily be converted into VBA, if needed, by adding the keyword 'Set' in front of the third line of code. That example code will only work when you are creating a new drawing, adding a new sheet, or adding a title block by code, not when doing those things manually. The 'SilentOperation' setting is essentially blocking all pop-up dialogs while it is set to True, then setting it back to False before the code ends. This type of setting has 3 levels of scope (amount of stuff it can control): Application level scope, everything iLogic related level scope, and specific iLogic rule scope. But all of those are only used when doing things by code, not when doing things manually (through interactive user interface tools).
I have attempted to catch and interact with (fill-in, then dismiss) the intermediate dialog that gets shown for filling in prompted entries in a title block that gets shown during the manual process using code based event handlers, but it seemed impossible. I can catch when the new sheet gets created and can even when a new title block instance gets created, and a reference to the title block on the active sheet after the title block gets created, but can not get a reference to that interactive dialog. We may be able to catch the event of creating a new instance of a title block 'before' it happens, then take over control of the event (handle it) to block the usual manual process from happening, then use code means to add an instance of a title block, using SilentOperation, but that would require a lot of complex code, and may be really difficult to control properly, due to lack of available information at that point in time. That sort of thing would normally be dealt with by a custom Inventor add-in though, not just some simple VBA macro, or iLogic rule.
However, if you know ahead of time exactly what prompted entries are going to be asked for, and what order they are in, and you already have all the values that you want to put into them, before you create the new drawing, new sheet, or new instance of a title block, then we can do the whole process by code, instead of manually, and can then fill in those prompt values by code, to avoid the dialog prompt. It usually just requires us to have those values ready, in the form of an Array of Strings, in the correct order, and with the correct number of entries (matching the number of prompts). Then we can supply that Array of Strings to the procedure for filling in those prompts.
Wesley Crihfield
(Not an Autodesk Employee)