MS Project Standard or Professional?

Maria 40 Reputation points
2026-03-19T08:40:48.26+00:00

I work with a team in Higher Education we manage our own projects and these are linked in a Master project. Our issues are:

updates made in our sub projects don't consistently push through/update in the Master even when the Master is fully expanded showing all tasks.

When saving and closing we often see read only option and have to create a new name

The date filter shows multiple occurrences of the same year e.g. 2025 will appear twice or three times in some projects - particularly in the Master.

I don't want to move to Professional version if these issues persist in that version too.

Microsoft 365 and Office | Project | For education | Other
0 comments
Answer accepted by question author
Alina Le 5,000 Reputation points Independent Advisor
2026-03-19T10:02:57.33+00:00

Hello @Maria

I am happy to help you look into this. To ensure I fully understand the situation, could you please provide screenshots of the two specific behaviors you mentioned?

  • Updates in sub-projects not consistently appearing in the Master project.
  • "Read-only" prompts upon saving and closing, which force a "Save As" action.

The issues you're describing syncing failures, read-only locks, and messy filters are actually symptoms of how the software handles file paths and "file bloat" within linked projects. These are not missing features in your current version; rather, they are part of how the software behaves when multiple files are connected. Because the core engine that manages these files is identical in both versions, moving to the Professional version likely won't fix these specific issues.

To support you, I have outlined some information below that should help you and your team move forward smoothly:

1. Synchronization and "Updates Not Pushing Through"

MS Project sometimes "pauses" its calculations to save computer memory. If the Master project is not prompted to refresh, it may fail to display new data from the sub-projects.

-What you can do:

Go to File > Options > Schedule and ensure that "Calculate project after each edit" is turned On.

User's image

*Tip: When you close the Master file and the system asks, "Save changes to sub-projects?", always click "Yes to All." This confirms the "handshake" and ensures all links are updated.

  1. "Read-Only" Prompts and Forced "Save As"

The Behavior: Think of the Master Project as a "lock." When you open the Master, it automatically "claims" all linked sub-projects. If a team member tries to open their individual sub-project at the same time, the system marks it "Read-only" to prevent data from being overwritten by two people simultaneously.

What you can do:

Use the Master Project primarily for reviewing and reporting rather than daily editing. Ensure team members close their individual files before you open the Master, and vice versa. Adopting this "one person at a time" protocol will prevent the "Save As" loop.

 If you still need my assistance, please come back with screenshots or any additional details so I can review it again and see if there’s anything more I can help you with. 

Have a nice day! 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in "our documentation" to enable e-mail notifications if you want to receive the related email notification for this thread

Was this answer helpful?

0 comments

1 additional answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-03-19T08:41:26.1533333+00:00

    The described behavior is related to how master projects and subprojects work in Microsoft Project, not to Standard vs. Professional edition. The context does not indicate that moving from Standard to Professional would change this behavior.

    Key points about master projects and subprojects that affect the issues described:

    1. Synchronization between master and subprojects
      • When a subproject is inserted into a master project, the two files are linked: updates made in the subproject are available in the master, and updates made in the master are saved back to the subproject’s source file when the master is saved.
      • The master shows each subproject as a summary task with a Project icon; expanding this summary shows the subproject’s tasks, which can be edited from within the master.
      • If the master and subprojects are still linked, changes in one should be reflected in the other when files are saved. If they are unlinked, changes will no longer synchronize.
      • The context does not describe any edition-specific differences here; this behavior applies to supported desktop editions (Standard and Professional) listed in the article.
    2. Read-only prompts and needing to save with a new name
      • When working with master and subprojects, each subproject is a separate file. If a subproject file is already open elsewhere or locked (for example, by another user or process), Project may open it read-only and then require saving under a new name.
      • The documentation notes that when the master is saved, changes to subprojects are written back to the subproject source files. If the files cannot be written (for example, because of access or locking issues), this can result in read-only behavior and the need to rename.
      • This is again a function of file linking and access, not of Standard vs. Professional.
    3. Date filter showing duplicate years
      • The context does not provide specific details about duplicate year entries in date filters. It does mention that when combining projects into a master, each subproject retains its own structure and critical path, and that formatting and some view aspects are stored per file.
      • Any anomalies in filters or views in a master are more likely related to how multiple projects and their views/filters interact than to the product edition.
    4. Edition choice (Standard vs. Professional)
      • The provided documentation explicitly applies to both Project Standard and Project Professional for the supported versions and describes the same master/subproject behavior for both.
      • The issues described (synchronization behavior, read-only prompts, and view/filter quirks in a master project) stem from the master/subproject model and file handling, not from features that differ between Standard and Professional.
      • Based on the context, moving from Standard to Professional would not inherently resolve these specific behaviors, because the master/subproject mechanisms are common across the desktop editions listed.

    For working with multiple projects and master/subprojects, the documented guidance applies equally to the supported Standard and Professional desktop versions. Troubleshooting should focus on:

    • Ensuring master and subprojects remain linked (not unlinked) when synchronization is required.
    • Verifying file access and locking so subprojects are not opened read-only.
    • Reviewing how views and filters are configured in the master vs. subprojects, since formatting and some settings are stored per file.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.