Duplicate your view with detailing. Then Duplicate with dependant.

You'd have to either use callouts or duplicate the 1/8 scale plan to get views at a different scale.

I'd make a 1/8 scale plan showing the overall dimensions, building/wall section cuts, etc. Then duplicate that view, change the scale to 1/4, and make your dependent views there. You'll probably have to play with the "Hide at scales coarser than..." setting for certain types of callouts that you don't want to show up in your 1/8 scale plan (i.e. detail callouts, floor transitions, etc.).

See my notes in your quote above.
We're doing this right now with a huge floor plate. Overall plan is at 1/16" scale to fit on a sheet. Then I have an overall 1/8" (parent) plan that is broken up into 5 smaller dependent (child) portions. The dependent views are what I place on my sheets.

Word of note: Annotation, section cuts, getting things to look just the way you want them to plot, ... all this should be done in your dependent (child) views. You'll learn. But when you cut a section in the Parent plan and then adjust the head/tail/etc. it doesn't always carry through correctly to the Child plans.

You create a parent view on the scale you want the partial views to be (duplicate with detailing). You don't use this View for anything else then to host the Dependent Views. Rescale and make Dependent Views. Use the Matchline tool on them...

I will also add to Leanne's comment. You will learn. Some things transfer to the child view. I would also recomend when doing somthing like this to have views set up as "Print" views and "Work" views. I have added a project parameter and modified browser settings so that I can make model changes in one view that dose not effect any other views. This cuts down on the accidental printing problems when you are on a dead line and when dealing with buildings where to fit them on a 30x42 you have to use 1" : 30'-0" and you have 7 child views at 1/8" scale. It keeps your browser much more organized to do it this way.

Ahh, okay. That makes sense now. I was missing the "duplicate the view" step, THEN do the dependent views. Thanks to all for explaining it to me.

Dude, you lost me. :laugh:

You should see my project. LOL I lose myself.

Add a project parameter in the views catagory called "View Use"

Have "Working" views (duplicates of your print views, these never get places on sheets, no annotation ect ect ect)
Have "Print" views (this are you final product, placed on sheets, they are the views you make look good)

You can then modify your project broswer orginization to group the two "view uses" together. This cleans up your browser a lot.

This helps a lot when dealing with buildings that need to be split up. You can do all you modeling and drawing in the "work" views and then all your annotation in the "print" views.

Leanne was was explaing that some of the annotation catagories will not chage from parent to child even thought they are dependant views. Once you have made the child views all your annotative changes should be done in those views.

One of my projects is the size of 3 football fields. I have 7 dependant views on 4 levels of the building. Browser orginization is key to good work flow.

Okay, the browser orginization makes sense. But why do you have working and plotting views? Is it simply so you can make model changes on a clean view without a bunch of annotations getting in the way?

Once my model is annotated and changes need to be made, it seems easier to do it with the annotation. That way I can revise the model and fix the annotation at the same time so I don't forget anything. It is a pain in the arse, though.

I'm just curious about your workflow. I may need to start doing mine differently.