Sure we have the "option" to store the scratchpad database in the project folder in previous releases, but it sort of worked against the reasoning of the project database in the first place. Having the "scratchpad" database local meant faster access for ACE, avoiding the lag time involved in accessing a network drive that is shared. I mean, the drawings were already shared, so we took a slight speed hit there. We did not want to further reduce processing speed by placing the project database on a network drive. Sure you might get the latest version of the database, if someone else made a change to a drawing, but the trade-off was speed. Besides, even if someone did make a change to a drawing that affected the database, your own local database would see the time code variance and refresh itself, or at least prompt you to. There always seems to be confusion about the project database. When I teach ACE I have my students blow away the database for a project they are working on, just to prove to them that, unlike similar programs in the market, with ACE the drawing still rules the database, not the other way around. All drawing data is stored in the drawing files themselves. The database is only a snapshot in time of the collection of drawings, so ACE can deliver quick reports, next available wire numbers, etc. As Jared points out with 2006 and 2007 ACE is maintaining the database locally while still keeping track of drawing changes in an expedient manner, even if the change is made by another user in a network environment.
Doug McAlexander
Design Engineer/Consultant/Instructor/Mentor specializing in
AutoCAD Electrical training and implementation support
Phone and
Web-based Support Plans AvailablePhone: (770) 841-8009
www.linkedin.com/in/doug-mcalexander-1a77623
Please
Accept as Solution if I helped you.
Likes are also much appreciated.