Add Rebuild/Freshen Database to Ribbon

[dougmcalexander]

There are times when it is necessary to use the Rebuild/Freshen utility.  In fact, I have to use it prior to exporting to Spreadsheet or I don't get the most up-to-date data.  But there are other times as well.  For example, when I abandon edits to a drawing and overwrite it from a backup of the drawing.  I need to force a refresh.  Sometimes I delete entire circuits using standard AutoCAD erase. I then use Rebuild/Freshen Database to be sure that the database is updated and AcadE doesn't make any future decisions that assume those wires and devices still exist.  Just day to day design work sometimes requires that the database be forced to refresh.  Of course we could delete the project scratch database but that requires shutting down AcadE, locating and deleting the file and restarting AcadE, which equals lost productivity.

I never needed a database rebuild until MDI mode was introduced. MDI mode requires much of the data manager, since a designer or a team of designers might be working on the same project with 10-20 drawings open, and the drawings are in a constant state of flux until finally saved. The data manager must track the live changes and reconcile with the saved changes, while also making decisions regarding component cross-references, part number updates, next available wire number, etc., all while reconciling current state (in RAM) and last saved state.  

We often throw curve balls at the data manager while we are creating.  But many of us know that we are doing so and we force a rebuild.  It would be nice if the data manager could keep up, no matter what we do. But until it can, please add the Rebuild/Freshen DB command to the Project tools ribbon panel.  See screen capture.

[dougmcalexander]

Icemanau, Brad, posted a separate idea to add an option to delete the project scratch database from within the software and have a new one built fresh without leaving the software.  This is a great idea!  Perhaps put this as a right-click option when you right-click over the project name in Project Manager.

[Anonymous]

I have to rebuild the database all the time, even for simple tasks such as source/destination signals, inserting panel components from schematic and updating reports on drawings. For large projects, a full rebuild takes a long time. To me this is a major issue and having your work out of sync with the database file just should not happen and not require a manual rebuild. How will you know if your data is current unless you do a rebuild? This has been a problem with all the the versions of acad I have used and I am currently using 2015.

[dougmcalexander]

The way the scratch database works is a trade-off for data integrity.  Programs that are database driven are more vulnerable.  Since AutoCAD Electrical stores drawing data inside of the drawing file, the project database is merely like a scratch pad for the software’s internal functions.  This is the reason the project database is called the project scratch database.  So, in a worst case scenario, we can delete the database and a new one will be built from the drawings.  The drawings are almost always intact, unless we do something ourselves to damage them, like using plain AutoCAD commands.  

The database driven programs store the drawing data inside of a database.  In some cases all projects are in one giant SQL database, rather than a dedicated database for each project.  If the database becomes damaged, the drawings become damaged.  

So there is no perfect solution.  Autodesk has fixed the issue that required a forced database rebuild prior to exporting to a spreadsheet for editing.  But there is still room for improvement.  Like I said before, I never saw a database issue when single document interface was the standard.  But AutoCAD allows it so Electrical must somehow deal with it.  I take comfort in knowing that I can always delete the project scratch database and get back to normal - something I cannot do with the database driven software.  I have another program, a hybrid that is no longer in production, that stores some data in the drawings and some in two project databases.  It represents a good middle ground but is still not 100% as reliable as storing all drawing data inside the drawings.

[Anonymous]

Just an FYI, I am now using SolidWorks electrical that is database driven, and I have not had any issues with database damage.

I understand that having the drawings store the data is secure, but when you need the drawings to interact with each other, and the database doesn't provide the correct information, its kind of pointless.

[dougmcalexander]

From what I have heard SolidWorks Electrical appears to be very good.  I rarely have issues with Electrical’s database, now using 2018, but I also make sure that I only use commands from the Electrical menu.  The one cheat is when I erase an entire circuit.  I use a crossing window to grip all wires and components at once.  But then I force a database rebuild.   The problem for Electrical is not people like me.  I know when and when not to use plain AutoCAD commands.  The problem is mostly for those who have not been properly trained.  The plain AutoCAD commands are still available via the ribbon. or by typing them at the command prompt.  Many who have moved to Electrical from AutoCAD tend to mix AutoCAD commands into their workflow, because of their past experience, and this is the cause of most database issues.  I have asked Autodesk to include a novice mode that disables AutoCAD commands that could cause problems, until the new user has become comfortable with the Electrical workflow, but alas that has not happened.  

I’m curious.  Did you take a training class for both AutoCAD Electrical and SolidWorks Electrical?  I have always taken a class for any software I purchased.  When I first got Wiring Diagram, before Autodesk acquired it and renamed it to AutoCAD Electrical, I attended training for Wiring Diagram.  Some might have reasoned that, since it was just an extra group of menus inside of AutoCAD, separate training wasn’t necessary.  Thankfully, our IT department insisted that we attend a training class. I’m sure that I would have struggled and possibly even abandoned Wiring Diagram had I not learned how to properly use it.  I had been using promis-e, and probably would have switched back to it, had our company not brought John Zwerlein in to teach us how to properly use the Wiring Diagram add-in for our AutoCAD.

[Anonymous]

Yes, I have had the training and make sure to tell my co-workers to use the AutoCad Electrical commands. One of the biggest issues for us is the signal source/destination not updating correctly until the database is re-built. 

[dougmcalexander]

Yes, I'm curious about that. I seldom, if ever, see issues with signal arrows. That seems odd.

[PawanBhat_PS]

if it is specifically about wire signal issues using source/destinations. there is a function that has been in AutoCad Electrical for some time. 

Command: AEUPDATESIGREF

his command updates signal source and destination cross-reference text and wire numbers, including stand-alone cross-reference symbols.

[pmccutcheon]

I still use Pallettes, made myself a pallette doohickey to rebuild the DB

Good idea on delete the scratch