To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95663


User nbrouard changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|UNCONFIRMED               |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from nbrou...@openoffice.org Fri Dec 26 20:36:58 
+0000 2008 -------
>When you distribute a new form then, the use of the Registered Datasource 
>name, 
>versus the hard coded path to a file should avoid this proboem totally.

Thank you very much and instead of hard-coded path in a 'connection-resource'
you need a 'datasource':

Instead of:
<form:connection-resource
xlink:href="file:///C:/Documents%20and%20Settings/brouard/Bureau/Dass45-6-old.odb"/>

you need, within the <form:forms form:datasource="Dass45-6-old">.

Despite my efforts to find the information I did not go through.

But if you get an odt form with hard-coded path there is no other solution than
changing the path in content.xml .

I am closing the bug because it doesn seem to be a priority.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to