1. You tried to write the file yourself. Soln - export a file, fill it out and then import back. I recommend using the dbase format. You can use MS Excel to open this format.
2. You may have exceeded the log width. Up to 48 chars only.
3. You may have exceeded the number of logs. Up to 99 lines only, please.
Alternatively, you can just attach files to activities using logs. Use this format if you want to do this:
"file://pathlongfilename.extension"
Good luck!
Jorge
Member for
22 years 11 months
Member for23 years
Submitted by Steven Oliver on Thu, 2003-06-05 13:09
Member for
22 years 3 monthsRE: Import and Export
Hi again!
Got that bit. Infact its finally going to be http:// once I get some time to indulge.
Thnx and big one to you.
:D
Neeraj
Member for
22 years 3 monthsRE: Import and Export
Hi Neeraj!
My pleasure. Anyway, the script was wrong. It should have been:
"file://drive:pathlongfilename.extension"
Sorry for the inaccuracy. I hope this helps.
regards,
Jorge Taguinod
Member for
22 years 3 monthsRE: Import and Export
Mr. Jorge!
Many thanks to you for File Linking operation. I needed it to attach method statements for certain critical activities.
:D
Neeraj
Member for
22 years 3 monthsRE: import and export
Possible problems:
1. You tried to write the file yourself. Soln - export a file, fill it out and then import back. I recommend using the dbase format. You can use MS Excel to open this format.
2. You may have exceeded the log width. Up to 48 chars only.
3. You may have exceeded the number of logs. Up to 99 lines only, please.
Alternatively, you can just attach files to activities using logs. Use this format if you want to do this:
"file://pathlongfilename.extension"
Good luck!
Jorge
Member for
22 years 11 monthsRE: import and export
The method which works fine for me is to EXPORT the P3 data to a *.wk1 file, specifying the range of log records to be exported.
Make the changes in the wk1 file and in P3 use this file to IMPORT the revised data.
As I said seems to work fine for me