Hello Sanders,
Thanks for your response. I failed to add some additional detail in my first post. Here is a breakdown:
Let's say I try to open this sdb file with a particular dgn file (a working file with multiple reference files attached to it) and it fails to open.
Then I try to open the same sdb file with a new copy of the same dgn and the sdb file loads successfully.
After a couple of successful sessions, the sdb fails to open again with the same dgn through which it was previously opened.
Then the process is repeated with a new copy of the dgn, and then all is well again.
I don't mind using a new copy of the dgn everytime the sdb fails to open, but the person opening these files is accessing the the dgn files from a remote site with a not-so-good internet connection. Since the dgn that we use has a lot of references attached to it, it takes an extremely long time(1-2 hours) to load each time a new copy is made.
I can send you the dgn via a private message but all its references will be missing.
Vinod
Thanks for your response. I failed to add some additional detail in my first post. Here is a breakdown:
Let's say I try to open this sdb file with a particular dgn file (a working file with multiple reference files attached to it) and it fails to open.
Then I try to open the same sdb file with a new copy of the same dgn and the sdb file loads successfully.
After a couple of successful sessions, the sdb fails to open again with the same dgn through which it was previously opened.
Then the process is repeated with a new copy of the dgn, and then all is well again.
I don't mind using a new copy of the dgn everytime the sdb fails to open, but the person opening these files is accessing the the dgn files from a remote site with a not-so-good internet connection. Since the dgn that we use has a lot of references attached to it, it takes an extremely long time(1-2 hours) to load each time a new copy is made.
I can send you the dgn via a private message but all its references will be missing.
Vinod