Importing and updating in P6

I understand this is an old problem that has been solved on various versions, just Google for the theme.

http://primavera.zxlm.cn/kb/prim72418

Still, even after Primavera solves the BUG if you import from other databases read the following article:

http://www.xenautilities.com/articles/problems-importing-primavera-p6-projects

Software that creates garbage just for the sake of it,

"The end result is that users that import projects for status updates have found that they must spend several hours after each update cycle cleaning up the mess created from the imported project."

Seems like Primavera database handling is still bad medicine, even if there are no loops issues. It is unbelievable there are no such issues in any other CPM Software, no matter how cheap, even when ORACLE is wired to deal with large databases. Guess this is the price you have to pay for choosing the easiest to use CPM software !!!!!

If you got a Web Version, consider granting access to the database to your Subcontractors or perhaps even when it sounds crazy why not requiring them to generate the xer files from any other software except P6, in this way maybe much of the garbage will not be generated nor transferred.

What happened to Primavera Contractor? Maybe Primavera knew about the issues when transferring from external databases.

Good luck, you will need a lot.