Hi Barry,
My test code in my previous post was very, very basic and did nothing more than open a file found on the server. The only variation that I had was whether to keep the new session of MS visible or not. As you noted, if there were actual operations that occurred once the DGN file was open, then certainly speed and mileage will vary.
I think I have found a fairly good solution for my situation. The solution was provided by Jon in his previous post. It involved using the -O command line switch. For my specific program/situation, I simply wanted to be able to turn On/Off levels in View1 of the active DGN file. By having the user launch MS with the -O switch (e.g., this can be done by creating a separate MS shortcut that has the switch included in the Target field) then all reference files get "ignored" (i.e., do not load).
In a test case I performed to process 23 separate DGN files the speed increased from 54 seconds (without using the -O switch) to 35 seconds (when using the -O switch). Saving approximately 20 seconds is pretty good in my opinion.
Your Titleblock Tags Manager tool looks very sweet! Nice job! I'm curious; are you processing tags in the active DGN file or in a reference file somehow? If the former, then perhaps you may want to use the "OpenDesignFileForProgram" (ODFFP) and particularly if your list of DGN files that you are processing is already found in Excel. If you use the ODFFP method, then I think you will note an even faster speed performance. Of course this is dependent on if by "processing" tags you are simply changing their values. On the other hand, if you are turning certain tag levels on/off, then the ODFFP method cannot be used.
Anyway, thanks for chiming in and sharing your thoughts. I appreciate it and have learned a few new things.
Kind regards,
Matt
