Any way to change which symbols appear in the legend? Microsoft Project |
- Any way to change which symbols appear in the legend?
- Project useful for production scheduling?
- Multiple Versions of Project
- Automated RAG Status Formula
- Tailored calendar view in Project
- How to account for 2 similar resources where one works faster than other
- How do I get a global view of all projects in Project 2003
- Specify different allocations % during a task?
- Gantt Chart Wizard Formatting
- Undo?
- Custom WBS Codes
- Show/Hide specific WBS Elements
- Date Calculation
- watermark in project
- per diem rates
- Update Data from Excel
Any way to change which symbols appear in the legend? Posted: 05 Jan 2005 08:52 AM PST Colin, To change the legend, change the "Name" field of the symbol in the Bar Style dialog box. If you want to hide a bar style in the legend while keeping the symbol in the Gantt Chart, add an "*" as the first character of this "*Name" Gérard Ducouret "Colin Higbie" <com> a écrit dans le message de news:%phx.gbl... may show |
Project useful for production scheduling? Posted: 05 Jan 2005 08:31 AM PST Thanks, Dave! "davegb" wrote: |
Posted: 05 Jan 2005 07:15 AM PST In article <com>, "Steve Scott" <microsoft.com> wrote: Steve, Yes. I have those same three versions installed and running under Windows XP Home for basically the same reason - so I can respond to posts from an assortment of users on this and other newsgroups. Generally I do not experience problems having all three versions on a single PC. John Project MVP |
Posted: 05 Jan 2005 07:13 AM PST You're welcome Scott. Thanks for the feedback. Julie "Steve Scott" wrote: |
Tailored calendar view in Project Posted: 05 Jan 2005 07:09 AM PST Yes, sorry. About the closest thing to flagged fields is the "marked" task choice, but you only have the choice of formatting marked tasks differently. Thanks for the feedback. Julie "Ridgeroad" wrote: |
How to account for 2 similar resources where one works faster than other Posted: 04 Jan 2005 04:50 PM PST There really is no satisfactory way to take into account slight differences in efficiency like that. I'm not really sure it matters in a context such as you describe anyway. When you put two resources together on a task like that, it implies that they are working together as a unit, a team, interacting with each other on the task. Thus the efficiency that governs progress will be the efficiency of the team and not its individual members. IF they are dividing up the work of the task and working on their portions independently, so A finishes his part in 4 days while B does his is in 6, for example, you really have two different, albeit similar, tasks and they should be listed separately in the plan. Remember, you always should try to have the resources you plan to put on the task in mind when you estimate the durations in the first place. -- Steve House [MVP] MS Project Trainer & Consultant Visit http://www.mvps.org/project/faqs.htm for the FAQs <com> wrote in message news:googlegroups.com... |
How do I get a global view of all projects in Project 2003 Posted: 04 Jan 2005 03:19 PM PST Hi Mark, Welcome to this Microsoft Project newsgroup :) Try using a master file as I explained in my series on Microsoft Project in the TechTrax ezine, particularly #17 & 18, at this site: http://tinyurl.com/2xbhc or this: http://pubs.logicalexpressions.com/Pub0009/LPMFrame.asp?CMD=ArticleSearch&AUTH=23 (Perhaps you'd care to rate the article before leaving the site, :) Thanks.) FAQs, companion products and other useful Project information can be seen at this web address: <http://www.mvps.org/project/> Hope this helps - please let us know how you get on :) Mike Glen MS Project MVP Mark Peterson wrote: |
Specify different allocations % during a task? Posted: 04 Jan 2005 02:15 PM PST Work contours are described in the help files. One of the easiest ways to see how they work is to set up a little experimental plan with one task, maybe 10 days duration, put a resource on it, switch to the usage views, apply the various contours and see how the hours get distributed. BTW, task type matters there so if I have a task with 10 days duration that's fixed work and apply a bell contour, the duration goes to 3 weeks. OTOH, if the task is fixed duration and I apply the contour, the total work hours changes while the duration remains at 10 days. -- Steve House [MVP] MS Project Trainer & Consultant Visit http://www.mvps.org/project/faqs.htm for the FAQs "fxs" <com> wrote in message news:%phx.gbl... |
Posted: 04 Jan 2005 12:55 PM PST Hi Glenn, Welcome to this Microsoft Project newsgroup The wizard is a quick way to format, but it does not cover everything. Try Format/Bar Styles../Text tab - it's all there for you FAQs, companion products and other useful Project information can be seen at this web address: <http://www.mvps.org/project/> Hope this helps - please let us know how you get on Mike Glen MS Project MVP Glenn wrote: |
Posted: 04 Jan 2005 12:17 PM PST Nope - there is only one level of undo and it is hard-coded and there's nothing that can be done about it except hope it will change in some future release. Sorry about that. -- Steve House [MVP] MS Project Trainer & Consultant Visit http://www.mvps.org/project/faqs.htm for the FAQs "Stefan Robert" <ca> wrote in message news:2005010415171675249%.. |
Posted: 04 Jan 2005 11:27 AM PST In article <#phx.gbl>, "fxs" <com> wrote: fxs, For a solution, see me response to your other post. John |
Show/Hide specific WBS Elements Posted: 04 Jan 2005 10:55 AM PST In article <#phx.gbl>, "fxs" <com> wrote: fxs, To answer your basic request I kept the code as simple as possible. If it is run a second time, the WBS prefix will get more "00s", and the code will need to be modified to handle WBSs for added tasks. If you have a little VBA experience, modifying the code to be more flexible would be a good exercise. If you do not have any VBA experience but would like to get the added functionality, write me direct and tell me what you want the WBS to look like (i.e. default WBS, a custom WBS structure, etc.). For example, if a task is added between existing WBSs, should the WBS renumber from the added task on (Project default) or should existing tasks retain their original WBS? John |
Posted: 04 Jan 2005 10:49 AM PST There're several issues to be explored here. Remember duration is the amount of working time units designated by the calendar between when work is first performed on a task and when it ends. It may or may not be continuous. If a task starts Dec 07 and goes for 5 days, then is interrupted for a few weeks (perhaps the holidays are shown as non-working time, a 2 or 3 week stand-down) and then resumes, working for another 5 days and then it's finished sometime in January the elapsed time is more than a month but the duration is still only 10 days because the time off in the middle for the holidays doesn't count. An alarm bell is going off when you say you "edited the start and end times" for the tasks. When you edit either one you inevitably establish constraints on the task, constraints that are rarely justifed. If you edit the start, you get a Start No Earlier Than constraint. If you edit the end, you get a Finish No Earlier Than constraint. If you edit BOTH, the constraint you get is determined by the order you do the edits. BUT, you really shouldn't be doing either one! The whole reason Project exists is to calculate the schedule for you - you don't tell it the dates where it should schedule the tasks -- you tell it what needs to be done, the relationships between the tasks, the resources you have to do them with, and how long each should take and then it tells YOU the dates you can have them on, a whole different paradigm. I'd suggest you be very, very careful about using the 24 hour calendar as you are. Doing so implies that when your 60 day task begins, work on it never stops for over 2 months, the resources doing the work never sleeping, never eating, never getting a day off for that entire period of time. People simply don't work that way. The project calendar should describe the hours during the day that work will take place on a typical task as scheduled for a typical resource. While your company may very well work 24/7, a single person most certainly does not and the tasks should usually describe the work done by a sigle person or a team working together as a unit. If your "standard" shift is M-F, 8-5 that should be your project calendar even if you really have multiple shifts working in the aggregate 24/7. If you have a task "dig a hole" and you assign that task to Joe Dayshift, the hours that Joe works are the only one's that matter - it is totally irrelevant that there is also Bill working Swing shift and Fred working Graveyard, they're not digging the hole, only Joe is, and the calendar that governs the scheduling of that task should be Joe's work schedule and Joe's alone. The project calendar governs task placement's until you assign resources and so, IMHO, it should be the work shift of a typical resource, not the company as a whole. HTH -- Steve House [MVP] MS Project Trainer & Consultant Visit http://www.mvps.org/project/faqs.htm for the FAQs "Cindy" <microsoft.com> wrote in message news:com... |
Posted: 04 Jan 2005 08:19 AM PST John Thanks, I would rather set an empy six pack of brew on it after beating the bushes... "John" wrote: |
Posted: 04 Jan 2005 02:19 AM PST This is true... which is why I generally use this type of resource as a "material" resource when tracking costs to this level. Sound advice! Thanks, Ian "Steve House [MVP]" wrote: |
Posted: 03 Jan 2005 07:11 PM PST Glad you made it. The later versions of project have a wizard to walk you through this confusion. -- -Jack ... For project information and macro examples visit http://masamiki.com/project .. "toast88" <microsoft.com> wrote in message news:com... sticking or your excel not reference an MSP Key select 30+ Excel |
You are subscribed to email updates from TextNData Forums - Microsoft Project To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |