Path for Links to Files

[Just a user]

I have linked files to elements. This works fine. When documenting with HTML the file links can be used and the actual file is transferred to the HTML structure.  
I need to hand over the library (*eap file) and its linkeed files to another organisation. The problem is that the path used ot the linked files, is absolute and from my personal perspective (e.g. Q:\mywork\ea\file\linkedfile.doc). If someone would take over the *.eap and the files, he would have to correct all the links (e.g. D:\somewhere\project\links\linkedfile.doc).
Has someone a solution or did I miss an option?

[Paolo F Cantoni]

I have linked files to elements. This works fine. When documenting with HTML the file links can be used and the actual file is transferred to the HTML structure.  
I need to hand over the library (*eap file) and its linked files to another organisation. The problem is that the path used to the linked files, is absolute and from my personal perspective (e.g. Q:\mywork\ea\file\linked file.doc). If someone would take over the *.eap and the files, he would have to correct all the links (e.g. D:\somewhere\project\links\linked file.doc).
Has someone a solution or did I miss an option?

"Replace in files" using a decent text editor? For the HTML output at least.

The whole HTML process out of EA - while an excellent concept - leaves a LOT to be desired in its current implementation.

About 3 years ago, I think, I made the observation that any file related content within EA should use the "Local Paths" process to allow exactly this kind of customization.  I DON'T believe this was done, but I stand to be corrected; since notwithstanding the large number of changes Sparx identifies in the release notes, there are other changes that are made but NOT identified...

BTW: I've previous done a search and replace directly into the relevant columns with MS Access to both an .EAP file and a DB (via Linked Tables).  So that's your option of last resort...

HTH,
Paolo

[Just a user]

Thanks. At least I know I didn't mis something in the manual. Your suggested workarounds are useful. I will look for a creative solution (e.g. editing the *xmi or a small VBA program).

[Eve]

I just did a test.  If you specify a file path relative to your eap file, it will work.  It does look like it isn't documented though.

Updating your existing links would require the automation interface or direct sql access.

[Just a user]

Thanks. I tried it before with the old DOS notation (e.g. .\files\linkeddoc.doc) and that did not work. The solution you suggest (e.g. files\linkeddoc.doc) works fine. So as long as you keep the relative directorystructure when moving the eap and the linked files this is the solution.
 8-)