Exporting to Excel

Yes, you need to install the RA environment on your machine first. Good luck!

Hello Hazel



my files are in P3win\Ra\samples\excel but I don’t think this is important. But it is important that files like P3engine and ra.dll are in P3win\P3Progs (happens during Installation of P3) What error do you get?





Hannes

Hello Devamalya De



I cannot send you those "two files" because of copyright reasons, if you have p3, you will have those files already (activity.xls and project.xls) but I will send you my translation file, based on the knowledge of those files.



Regards Hannes

Dear Hannes,

Wish u a Happy 2006. I’m intereted in having the two files in my inbox. Plzzz mai me the same at: dev2k5@gmail.com.





Regards,

Devamaya De

Those two files don’t have anything to do with exporting - but they are excelent! You can read and write all data from P3 (also a resource-list or a WBS-list.) I used the idea for a (quit perfect) translation from MS-Project to P3.



Interested ? send me your email-address

yes I see your point.



I have the two files.

But I have found them to be slow (connection type wise) and not flexible (format wise).



manually creating a DBF and only writing the data you need still seems to be a better option.



thanks for the input.



Gün. :)

I have used for several years two Excel files found on the P3 3.1 installation disk in a folder called Ra\Samples\Excel.

One is called Activity.xls

One is called Project.xls





If you have access to these they may go a long way to shortcutting your process.

you are welcome.



I dont agree with you regarding the difficulty of the export/import utility of P3. DBF is still second best to xls. so we here are trying to do our best with limited options. and a s..t word still escapes from my mouth everytime I forget to apply point 3 and do an import. worst is when you dont notice an unsignificant little piece of data missing till it really messes up the chart or calculation (happens rarely). expecially when time is running out and they are waiting for you at the next meeting.

I dont understand why Primavera didnt yet publish a module to add good xls export/import functionality to their program (if only to remove the need for point 3 to be applied and yes thats a rarely known clue).



A program must be easy to use. the main effort of the user should go into the work itself not into the import/export problem for example.



now that they have the experience and the know how to export/import to/from xls with the P3ec v5.0 they can use it to do a little module for P3 v3.11 too (wishfull thinking).



I still hope they do. even though Primavera probably wants its users to convert to P3 v5.0. a simple module to add a simple import/export of xls tables will in my opinion be very well recieved by the P3 v3.11 users community.



Gün.



/snip/

the common belief that the exporting function of primavera are difficult to handle could have been proved wrong.

/snip/

Hello Gün,



I first disagreed with your point 0, but after reading point 3, I must say that I’m back to the dbf-format, as this is a very good hint.

Version 5 has EXCELLENT import export to Excell, Probabably "!better" than the old 16 bit product.

Exporting and importing files from P3 is a real mess.

For P3ec it is nonexistent completely. :((( That’s the only reason why I had to revert to P3 v3.11. anyway, back to the subject.



0. Use only DBF export.

1. You will be spared the number of rows restrictions for WK1 files.

2. My experience is DBF files are more robust.

3. Don’t bother to paste inbetween or insert or whatever in Excel. But then fix the file BEFORE saving with Insert/Name/Define/Database(choose up and leftmost cell and down and rightmost cell) (this is a little known clue. had to read the DBF format specs someplace).

4. You can also select ALL of the data in the cell and save the file while all are selected (surprisingly it works but have found no documentation regarding the issue).

5. If format errors then copy/pastespecial/format from line one (or known working file) to the problematic areas (problems most probably are: lengh, date format, text read as number).

6. If problem with text showing as number then use ’ before the value then "enter".

7. to not lose some characters from the TITLE column keep it wide before import. Also choose "Definition length" as 48 before export.



These are the little bits of information that come to my mind on short notice. Will post more when/if I remember them but this short list should be very useful to everyone as is.



=====the following will be a new post=====

by the way,

Has Primavera figured a way to import Excel files (or txt, any file) to P3ec and made it public?

any information will be very much appreciated.

import from access will do too.



I can’t import while using P3ec.

=====end new post=====

Hi Manu,



Or perhaps yu can convert to MS Project first (as what yu’ve told me)....then from there yu can do lots of things i.e. once yu are in MS Project, yu can easily copied to MS excel...copy and paste only. That’s the reason I like to use MSP.



Thanks



norzul

Always use the dbf format. Remember that you cannot "add" rows when using this format, you must "insert" them.

Hi Manu,



Try to reset/refresh your Export Definition File. Or try to use a different Filename of your exported file. Or you may use file Type other than Wk1.



Regards,

Sen