Hi Barry,
Thank you for the suggestion. In the past I think I casually experimented with the ApplicationObjectConnector (AOC) method, but I was unsuccessful with having it manipulate the View object with turning on/off different levels. The attempt to turn a Level "off" never held after-the-fact. Nevertheless, I think I will do a quick experiment and see if this is still the case.
You asked:
Is there any reason why you are doing this in VBA instead of a batch process?
Not really except that I already have a separate Excel VBA program that allows a user to drag/drop the desired DGN files into a ListBox on a form that then generates the list of DGN files into an Excel Worksheet. Within Excel the user can then sort the list, add columns, etc.. Anyway, in my MicroStation VBA program the user then selects the Excel file to process the different DGN files. A very small benefit to this approach is that I can then also make a note in the Excel file if the VBA "succeeded", "failed" or if the DGN file was "Read Only", etc. This approach, while not related to my original post, is also useful if say I want to change the value of a Text object in each DGN file with a new value that is listed in the Excel worksheet. The value of the text would or could be unique to the filename/path listed in the Excel worksheet. To me using the Excel file is easier than trying to create an array or matrix that would be hard-coded in the VBA or say read from a TXT file.
Nevertheless, you are correct that for simple operations the Batch Process approach/method is very slick. I have successfully used it in different instances for different situations.
Thanks,
Matt