PDA

View Full Version : Copy detail sheets to other projects ADT 2005



gregb
2006-09-19, 12:03 AM
I've seen a lot of people asking about methods for creating detail sheets so I thought I'd share a method I just learned today.

I have four projects that will be using identical detail sheets (why the buildings are not all in the same project is a long story so please just accept the circumstances as a teaching tool) and I've be struggling with the best method for copying the detail sheets from one project to another. I have about a dozen detail sheets; each with up to thirty details per sheet. Each detail is a separate view file with a single model space view.

The detail view files are copied from the original project by dragging them from windows explorer directly into the project navigator (holding the Ctrl key down while dragging will create a copy). The sheet file is then copied to the new project by copying in windows explorer and pasting to the sheets tab of the project navigator. In order to do this the sheets tab must be in the explorer view. For some reason this process keeps the names of all the model space views placed on the sheet but deletes the numbers so each view needs to be renumbered.

Since this process maintains the original external reference paths, I then go to the Reference Manager program and update the paths of all the details to the new sheet. Once this is done all of the detail numbers and titles need to be linked to the new sheet by opening each detail and dragging the callouts to the appropriate detail on the new sheet.

It sounds a bit cumbersome but so far it's the best method I've found. Hope this is clear and helpful.

Steve_Bennett
2006-09-19, 04:23 AM
Excellent tip Greg!!! This is exactly the type of stuff we want to see in the tips and tricks forum. Keep them coming guys!

tatriest
2006-09-19, 04:31 PM
Greg, try this next time............ copy the associated XML with your View drawings. This might carry the numbers with it??

Terry

gregb
2006-09-20, 12:05 AM
Interesting. I tried copying the xml file after copying the sheet to the project navigator without any apparent changes. A new xml file is automatically generated when pasting the sheet so I saved over that with the file from the original project and it didn't seem to have any effect. I then copied the xml file to the new project before copying the sheet and I was prevented from pasting the sheet to the new project.

tatriest
2006-09-20, 10:58 AM
When I opened both the VIEW and SHEET xml files, it appeared that the VIEW xml had the 'linking' information.

I am going to try it when I get to work.

tatriest
2006-09-20, 04:14 PM
I could not get the linking to copy over........................

agoodmansen
2006-10-04, 11:59 PM
...Wish I would have seen this post two months ago... We attempted many different things, and ultimately did a similar process as you have described. I tried the Autodesk discussion forums first (with no luck), but didn't even consider checking the AUGI forums... I'll be checking back here more often now!

Jay Zallan
2006-11-21, 08:21 AM
Excellent tip Greg!!! This is exactly the type of stuff we want to see in the tips and tricks forum. Keep them coming guys!
Yes great tip but 2005??? That release was so limited when compared to 2006, let alone 2007!!!

Join the evolution folks, don't become dinosaurs...that software is 3 actual years old and in computer time that's nearly ancient!!! oh and BTW it will be extinct in 16 months...

Steve_Bennett
2006-11-21, 08:31 AM
Yes great tip but 2005??? That release was so limited when compared to 2006, let alone 2007!!!

Join the evolution folks, don't become dinosaurs...that software is 3 actual years old and in computer time that's nearly ancient!!! oh and BTW it will be extinct in 16 months...May I suggest you check out the My Feedback Portal (http://myfeedback.autodesk.com/)? You can cut that leap now by signing up to participate in betas...

LOT's of firms are still on 2005 - it was a rather popular release for some reason...

gregb
2006-11-21, 09:06 PM
Hey, that sounds like a great idea. I'll upgrade immediately. When should I expect to receive your check for $60,000 to cover the cost of the software?

Steve_Bennett
2006-11-21, 09:19 PM
Hey, that sounds like a great idea. I'll upgrade immediately. When should I expect to receive your check for $60,000 to cover the cost of the software?Don't hold your breath. That's why I suggested the beta program. you get to test out the new software before it's released and provide feedback!

Brian Myers
2006-11-22, 04:22 PM
Yes great tip but 2005??? That release was so limited when compared to 2006, let alone 2007!!!

Join the evolution folks, don't become dinosaurs...that software is 3 actual years old and in computer time that's nearly ancient!!! oh and BTW it will be extinct in 16 months...

Ultimately it's about productivity and your business model. To justify keeping/upgrading software you need to look at the following:

1) Employee training. - Will they get the most out of their software or will they use it like every other release? Without proper training getting a new release may not be worth the money.

2) Economics - Not everyone can afford new software. Even if they can afford it, if they've achieved a high level of productivity with their current software they might not be able to justify a "minimal" increase in productivity compaired to the cost of the new software.

3) Employee happiness - Sometimes a happy employee is one that gets to keep their old office standard. Sometimes its an employee that gets the latest and greatest. In this regard you need to weigh your economics along with your employee rentention value to decide if your current software solution is the best for your organization.

4) Growth - Is your company growing and needs more seats of software? Are you getting smaller from efficiency or lack of work? Each case provides an interesting twist to what your future software requirements will be.

5) Job requirements - Has the software changed enough that your current software is not able to work with the data provided by other individuals?

6) ADT 2007 isn't backwards compatible when dealing with AEC objects. If your contractors use older versions of AutoCAD/ADT then perhaps a company that really uses ADT as ADT might not be well served to upgrade to the latest version.

There are other reasons as well, but I'll stop with the top 6. Being a Dinosaur has nothing to do with the software you use, it relates to business direction. Will your business do better with newer software? You are a Dinosaur and eventually will face extension if you don't meet market demand with your deliverables and can't compete with those in other firms. If you are still profitable and producing deliverables you and your customers are happy with then you are pointing your firm in the right direction. If you are overlooking a greater profit margin and happier employees by not upgrading then a Dinosaur or endangered species you may someday become. It's still easy to be profitable using ADT 2005 software... now if you are still on AutoCAD r14 or 2000 and doing architecture I might question your business direction if you've not taken the time to analyze the benefits of an improved package. BUT if you've itemize the benefits of the new software and realize that AutoCAD v.10 will work just as well for you as 2007, then good for you... don't upgrade (but I might still question your decision a bit just so you understand the power you might not be realizing in your day to day business).