Skip to main content
Apr 17, 2019 12:16 PM UTC
Archived

Better error messages - not everything should be ">>>> error <<<< Internal Error (001) occurred..."

">>>> error <<<< Internal Error (001) occurred..."  seems to be a default that is attached to too many problems.

Recent issue was that you cannot use cross sheet graphics if the Def_sheet_format is protected, even though the graphics do not appear to have any connection with that layer and were not being placed onto it.

The admonition to run the check database routine almost never reports any issues (in this case it was NOT a database issue) and it requires the work to package up enough information for diagnostics and a file a support request for something that a reasonable error message should take care of.
The ">>>> error <<<< Internal Error (001) occurred..." message should be reserved for actual corruption of the database or a program error.  Anything significant enough to create it, should be considered a programming issue.

2 replies

Apr 25, 2019 2:14 PM UTC
Status changed to: Acknowledged
olivierlp
Community Manager
Jul 5, 2023 3:08 PM UTC
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.

Olivier