https://bugs.documentfoundation.org/show_bug.cgi?id=155255
--- Comment #3 from lostbits <aschw...@acm.org> ---
I thought that I'd put this in as a request for an enhancement, not as a bug.
Sorry about the confusion.
What is requested is that the DB used within the document be moved with the
document when necessary. In this regard there are two cases:
[1] A move on the same computer within the same user account, and
{2] A move to a source external to the originating computer and user account.
In [1] there is no change needed. That is, going from the same user to the same
user allows access to the DB (if absolute paths are used). If absolute paths
are not used, then the DB must be moved also or a path the the DB generated.
In [2] a change is needed. Both absolute and relative paths are no longer
valid. If on the same machine then there are security issues. If on different
machinges (or the cloud), the DB is unavailable.
The suggested solution, eg, manually moving the DB, will work providing the
Data Source is changed appropriately. But, as an enhancement, it would be
desirable for LO to do the suggested operations on the users behalf. If
elected, this requires an augmented interface to include copy, move, rename of
a given document, or the conversion of an external DB to an internal DB. The
conversion is stated to be possible, so the issue disappears, but there does
not seem to any mechanism to do this within (at least) Writer.
The existing Bibliographic documentation provides no guidance on any of these
matters, to wit, moving, copying, renaming the LO Writer document or changing
an external DB to an internal one, nor is there any description of any of
these. And to the point, my volunteering of documentation services has been
silently rejected, hence, I have no means to contribute to this effort.
--
You are receiving this mail because:
You are the assignee for the bug.
