still finding lots of issues in files that it seems only V8's verify dgn is capable of fixing.
Are there any plans to update this to Connect, or provide some kind of file fixer?
I see from other threads that there is a tool FixRange? however NO documentation. where is this, how do I use? I have been able to load using mdl load FixRange but then can find no tool, or key-ins to run????
VerifyDGNThere is no Connect version of this tool. If you have any file related issues, kindly log a Service Request and email the files for review.
FixRangeRe-evaluate the cached ranges of all elements in the file.Load/Execute: mdl load fixrangeKey-ins: set rangeLinks: click here
however submitting file related issues is not a practical solution. Support is not generally the quickest for a start so expecting us to send a file off and wait for it to be fixed is not workable.
As is normal, these kind of issues do not show themselves when we have acres of time to spare, generally they occur at the business end when time is of the essence and affect multiple files or references. I need a way that I can fix these things without having to resort to support.
Can we list out the known issues. If we know what are the issues then we can check if these issues can be fixed.
There are Users accessing files over network and for various reasons the file is corrupted at DocFile level.There is very little chance of recovering the file and can only be restored from the backups.
Very rarely(using ms for around 15 years now) I could probably count on the fingers of both hands the number of times I have had a corrupt file that I was not able to recover.
A start of a list, but not extensive:
1. ms crash when selecting element (usually a cell of some type)
2. ms crash when attempting to exchange into reference file
3. ms crash when attempting to export file
4. ms crash when attempting to edit element
5. ms unable to select all or fit all to view
6. ms unable to open file without crash
7. ms crash when attempting to copy elements into live file from reference
verifydgn seems to correct a lot of issues like this. I just don't understand why it was removed, what harm would it do if it was left in?
Thanks Duncan for this list.
To take it forward we will require supporting files for each of those cases. Additional details like which software/version/format these files originated from will help.
It may take a while to collate definite examples of all these Leonard as we tend to fix, or remake when encountered.
I too find it crashes more frequently than v8i, but it's clearly not file dependent. Just happens randomly. I can say I haven't lost work or corrupted a file in years.
"Reproduce the error, please describe the steps to cause error and include file" is Bentley speak for wtf. I've been on this bus for a few weeks now. Very time consuming and often not fruitful. The techs have been very helpful, just not always real knowledgeable. It is hard.
Always been curious, what happens to those little message we send off when a crash happens? You may not always get that particular option, but I've sent off dozens.
Connect r15 10.14.00.109 self-employed