Good day all,
I've encountered an issue with certain DGN files. We use custom properties to store data related to the jobs in our DGN files, this data is used by some VBA routines that we use in our office. In some rare cases, these properties seem to get corrupted, and once that happens, I am unable to fix them. If I right click on the DGN in file explorer and switch to the Custom tab, it will crash file explorer, as well. It seems to happen only to DGN files that contain elements imported from outside files, but there isn't any apparent pattern to the sourcing of this external data: I've got one on my desk now that has had a DWG file referenced in and merged into the master, but it's also happened to files with DGN files and Esri Shapefiles attached (without being merged in).
Is anyone familiar with this issue?
In the cases where this happens, all work on the files grinds to a halt as a result of this issue. Any help would be appreciated.
Hi Darin,
Darin Rodberg said:Is anyone familiar with this issue?
I did not see many projects when file custom properties were used. But for these cases, I do not recall any such problem.
On the other hand, I found several discussions on this web about strange behavior when custom properties are added manually and/or using VBA API. So probably some issues or bugs exist in the code.
Darin Rodberg said:In the cases where this happens, all work on the files grinds to a halt as a result of this issue. Any help would be appreciated.
Because you mentioned the situation is rare, I assume it cannot be reproduced easily. In such case I recommend to create Service Ticket and to share the corrupted file(s). Maybe developers will be able to analyze and to "back track" how and why the file was corrupted.
Darin Rodberg said:It's in the tags.
I understand why Rod thought about tags in MicroStation elements :-)
BTW There are best practices defined and it's recommended to share product and exact version information in the text. I like what is common in MicroStation Programming forum: To use standardized subject format [<product> <version> <API>] Issue (modified to this post it can be [MStn V8i SS4] Corrupted custom properties, because it greatly simplifies understanding of question.
[<product> <version> <API>] Issue
[MStn V8i SS4] Corrupted custom properties
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan Šlegr said:standardized subject format [<product> <version> <API>] Issue (modified to this post it can be [MStn V8i SS4] Corrupted custom properties, because it greatly simplifies understanding of question.
Another benefit, it provides community members with important info without needing to open the thread. That leads to less speculation and more relevant responses.
Regards,Ron