Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Drawback of P3 usage

2 replies [Last post]
Shahzad Munawar
User offline. Last seen 6 years 30 weeks ago. Offline
Joined: 2 Jul 2003
Posts: 551
Groups: None
It is noticed with great concern that P3 has a big flaw of auto saving. There should such command that the changes in P3 tool should not be auto saved without Planner’s consent as usually done in excel, word and MS project where these softwares ask before saving any data ?

What’s your opinion?


Bhuvaneswaran Vel...
User offline. Last seen 3 years 28 weeks ago. Offline
Joined: 28 May 2003
Posts: 19
Groups: None
Also, autosaving is one of the good feature in the database management which will reduce our time for saving the records after periodical data entry.
Most of the other office softwares (even x-l, word) are also having the function of Autosaving by default while installation itself.
User offline. Last seen 1 year 26 weeks ago. Offline
Joined: 27 Feb 2002
Posts: 552
Groups: None
P3 is a database software. I think most scheduling software is a database architecture.

In database design, data will be saved by press submit (form base input) or goto next record (table form input). Alternative, input data are save in a temporary location and will not sync the physical database until press save, which is your suggestion.

The disadvantage of the alternative is double a database structure and sharing is limited.