Issue 19387 - Save datasource information to file
Summary: Save datasource information to file
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: All All
: P3 Trivial with 5 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-10 12:44 UTC by fabienst
Modified: 2013-02-07 22:34 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description fabienst 2003-09-10 12:44:50 UTC 
Hello, 
 
I think it would be nice if the datasource information (used for example to do 
mail-merge) was save in the Text (sxw) file. 
 
Currently it is saved on the disk, and if the file is opened from another 
computer, the data source connectivity information is lost. 
 
So you could save datasource information used by the document in the 
file/document itself. 
 
What do you think of that ? 
 
Thanks, bye.
Comment 1 gieschke 2003-09-11 13:34:15 UTC 
I think this is a duplicate of Issue #16146.

But it's definately NOT a stopper to OOo 1.1, so please change the
target milestone.
Comment 2 fabienst 2003-09-11 14:25:51 UTC 
It looks indeed like issue 16146. 
Just to be sure I will explain here what feature I expect. 
Yes I would like to have a per-document DB context/ Datasource. I 
mean in my document (docA) I would like that all information 
concerning a datasource (datasourceB) - like tables, queries, links 
- be saved in the document. In fact it would be nice if it were 
possible to choose either to save it (datasourceB information) into 
the document or globaly for the user. 
This is for example useful (per document datasource) when sharing 
files accross a network so that the network administrator doesn't 
have to specify datasource information on every computer and user 
account) 
The idea of an "explorer" seems nice, that way it would even be 
possible to drag and drop datasources from one location to another 
(eg from global datasources to per-document datasources) 
 
According to the issue 16146  the request was essentially for 
queries, but it could be for a complete datasource (includinf 
queries, tables, datasource format/access...)
Comment 3 jogi 2003-10-01 15:05:23 UTC 
JSI->MIB: Which target do you think is realistic?
Comment 4 michael.brauer 2003-10-13 09:57:33 UTC 
It seems to me that we should have a look at this bug together with
issue 16146
Comment 5 hans_werner67 2004-02-02 12:20:34 UTC 
change subcomponent to 'none'
Comment 6 bettina.haberer 2010-05-21 14:52:31 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".