To all database systems I know, there is NO "undo" function, especially the data is in sharing mode.
Consider the situation, you make a change on Field 1, other user may base on you latest input to process his business. Then you "undo" the value in the Field 1, how about other users? How to inform others for your "undo"?
If there is a system say they can "undo", the mechanism is the system keep your changed value to somewhere and will not update the database until you confirm. If we assume all user like have this function, then we need consider when submit the confirmation to the database is the best since the data you retrieving is not an updated one.
I think in future, "UNDO" is not happen on P3, P3e, P3e/c and TeamPlay.
… and there is a good reason for this. (Your English teacher would be horrified to read your posting.)
MS Project has an undo button. In fact, the schedule changes are not saved until you purposely do so. MS Project also does not allow for simultaneous update access to the same schedule by more than one person. In fact, even the ‘multi-user’ server version of MS Project only allows one person at a time to open a schedule with update privileges. This is a direct result of the undo function. The schedule resides in your computer’s memory and can be reversed-back. If the schedule is in your computer’s memory, it can’t also be somewhere else at the same time; hence only one person has update access to the schedule at a time.
P3 and P3e/c allows more than one person to have update privileges on the same schedule at the same time. This is truly what is meant by ‘multi-user.’ The reason that P3e/c can do this is that every time you update an activity, these changes are automatically returned to the ‘real’ schedule database. Some other person working on the same schedule will see that activity revision as soon as you make it. This is the basis of true multi-user, relational databases.
While it is still possible for an undo function to be built into such a system, it is much more difficult. In this case, an undo would be a reverse update. While possible, this would entail a tremendous amount of rewriting of every function performed and a lot of overhead. You would probably need to upgrade you computer to handle it. Still, it might happen (but not in P3.)
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
To all database systems I know, there is NO "undo" function, especially the data is in sharing mode.
Consider the situation, you make a change on Field 1, other user may base on you latest input to process his business. Then you "undo" the value in the Field 1, how about other users? How to inform others for your "undo"?
If there is a system say they can "undo", the mechanism is the system keep your changed value to somewhere and will not update the database until you confirm. If we assume all user like have this function, then we need consider when submit the confirmation to the database is the best since the data you retrieving is not an updated one.
I think in future, "UNDO" is not happen on P3, P3e, P3e/c and TeamPlay.
Thanks for your reply Ron, while I try to understand what your message is, I shall take it as "no" for the moment.
The answer is “yes,”
… and there is a good reason for this. (Your English teacher would be horrified to read your posting.)
MS Project has an undo button. In fact, the schedule changes are not saved until you purposely do so. MS Project also does not allow for simultaneous update access to the same schedule by more than one person. In fact, even the ‘multi-user’ server version of MS Project only allows one person at a time to open a schedule with update privileges. This is a direct result of the undo function. The schedule resides in your computer’s memory and can be reversed-back. If the schedule is in your computer’s memory, it can’t also be somewhere else at the same time; hence only one person has update access to the schedule at a time.
P3 and P3e/c allows more than one person to have update privileges on the same schedule at the same time. This is truly what is meant by ‘multi-user.’ The reason that P3e/c can do this is that every time you update an activity, these changes are automatically returned to the ‘real’ schedule database. Some other person working on the same schedule will see that activity revision as soon as you make it. This is the basis of true multi-user, relational databases.
While it is still possible for an undo function to be built into such a system, it is much more difficult. In this case, an undo would be a reverse update. While possible, this would entail a tremendous amount of rewriting of every function performed and a lot of overhead. You would probably need to upgrade you computer to handle it. Still, it might happen (but not in P3.)
Good luck!
Ron Winter.