wow its really interesting for me when i back to planning after 1 year :-)
any way
i had same problem and i found following solution for it at planningplanet. i hope it would be useful for you.
--------------
This is a known defect with Primavera 5 with the combination of SQL Server, Paste Project, and User defined Activity fields. See prim30231 in the Support knowledgebase.
You have two workarounds that will resolve this.
1. When copying projects, organize the projects screen by something other than EPS. Problem is only when pasting and you are organized by EPS. Or
2. Add the following setting in the PM.INI file in the section [Options]
UseSPToPasteProject=0
Solution 2 will force the program to not use a stored procedure used when copying. Problem is with the stored procedure.
RE: P3e / P5 Export function vs Copy (of Schedule) on UDF
It works properly and i dont have any problem
have a nice time
RE: P3e / P5 Export function vs Copy (of Schedule) on UDF
Hi Ronald,
Thx for the Service Pack #2 info. Passed it to our IT department.
Hi Amir,
Thx for the 2 workarounds. I tried both and both work.
One thing I found is that it now takes 3x as long to finish a "copy & paste" operation.
Did you find it the same in your environment ?
RE: P3e / P5 Export function vs Copy (of Schedule) on UDF
wow its really interesting for me when i back to planning after 1 year :-)
any way
i had same problem and i found following solution for it at planningplanet. i hope it would be useful for you.
--------------
This is a known defect with Primavera 5 with the combination of SQL Server, Paste Project, and User defined Activity fields. See prim30231 in the Support knowledgebase.
You have two workarounds that will resolve this.
1. When copying projects, organize the projects screen by something other than EPS. Problem is only when pasting and you are organized by EPS. Or
2. Add the following setting in the PM.INI file in the section [Options]
UseSPToPasteProject=0
Solution 2 will force the program to not use a stored procedure used when copying. Problem is with the stored procedure.
RE: P3e / P5 Export function vs Copy (of Schedule) on UDF
The Primavera Knowledgebase says that this was a known problem in Project Management 5.0 and has been corrected in Service Pack 2.