SOTL wrote:
True, Base does not support linked tables from a secondary datasource insideof a database file. OO.o however does allow one to work with multiple databases at a time. One example of this can be shown using your two test databases. If you open a writer document and bring up the control toolbars you can add a dataform control and then field controls for a single record from Test_Database-1 to this document. Now using the forms navigator add a child dataform control to the first and attach it to Test_Database-2. You can link these two dataform controls to each other via the COMPANY-NAME field in each. (You must recognize that there is no way for OO.o to insure that this relationship is valid, but so long as the data type of the fields match it will be accepted). Now finish up by adding a table grid to the form, belonging to this second dataform control. Run the form and you will see that indeed data will be presented to you from both databases.On Saturday 11 March 2006 04:30 pm, Mechtilde Stehmann wrote:Hello, Now, you cannot duplicate the above form with an embedded form from any one of the Base files, as in this case the dataform controls must all reside in the same database. This could be considered a short coming, then again it rather makes sense as the form is now aggregating data from multiple source so perhaps should be seperate from any one of them. Another limitation is that you can not build a select statement joining tables from multiple databases. However, in the same vein as the form example you can indeed use selection criteria from one database to pull data from a second. In this case one would create multiple connection objects using your favorite scripting language. The simplest case would be to duplicate the work done by the above form. You could create a prepared statement that selects records from Test_Database-2 and uses a parameter for the key. The value for this parameter could be read from a connection to Test_database-2. This is interesting but not much more useful then the form. You could extend this however, instead of a simple select statement you could use an insert statement, or a select into statement. In this scenario the routine could be written to loop thru any number or identifying records in the first database and move data from the one into the other on an as needed bases, make the table that it is inserted into a TEMP table and it will always be so. Once the routine is finished you can use this TEMP table to do whatever data mining functions your require. The bottom line is that the lack of linked tables, while an inconvienence in some instances, does not mean one can not use OO.o ( or Base more specifically ) as an aggregator of information from multiple datasource. The major problem in this type of system is one of relating data from the one database to the other, and for this even if linked tables are supported the problem is not alleviated. It will always be the job of the developer and business analyst to insure that this is done properly. In your last post I believe you are creating a bit of straw man. Base, or for that matter the database component of pretty any office suite you pick will not be the solution best suited to every data mining application. More often then not building the type of system you describe would best be done utilizing tools from a number of vendors. At a minimum it will require the creation of custom code to perform the data linking, extraction and aggregation - no matter whose tool you use. Drew Jensen |
- [dba-users] How does one access two databases at the sa... SOTL
- Re: [dba-users] How does one access two databases ... Mechtilde Stehmann
- Re: [dba-users] How does one access two databa... SOTL
- Re: [dba-users] How does one access two da... Andrew Jensen
- Re: [dba-users] How does one access two databases ... Alex Thurgood
