Apache OpenOffice Wiki - User contributions [en]

Symphony

2012-05-20T18:34:57Z

R4zoli: correcting typo

IBM announced plan to contribute Symphony code to Apache Software Foundation on July 15, 2011.
The code will be available soon.

This page is special for the code contribution effort.

==Introduction of the code base==

Symphony is quite like OpenOffice with an Java Wrapper. The code contribution doesn't include the Java wrapper which is based on Eclipse. So if you try with the binary build provided below, you will see the property sidebar, but not the MDI view in Symphony.

==Where to get the source code==

the code will be checked into: (Not ready yet)

https://svn.apache.org/repos/asf/incubator/ooo/symphony/trunk

==Build guide==

Please follow [http://wiki.services.openoffice.org/wiki/How_to_build_Symphony%27s_source_code this guide] to build Symphony's source code.

==The binary build==

You can build this out yourself by following the build guide. You can also get it from link below.

*[http://people.apache.org/~zhangjf/symphony/build Symphony binary installation package]

Please notice that if you have Apache OpenOffice.org 3.4 installed already, you need uninstall it first. Or you can install it parallel to Apache OpenOffice 3.4 by following guide
*[http://wiki.services.openoffice.org/wiki/Run_OOo_versions_parallel desribed here]

==Feature Description==
*[[Symphony contribution]]

==FAQ==

Q: What is the difference between this build and Symphony?

A: Since the java part of Symphony is not contributed. Feature, like MDI, Home page and Embedded browser in Symphony won't be available in this build.
And menu, toolbar, statusbar also have different look&feel from that in Symphony.

The Mail Merge panel in Symhony is implented in Java. It is also updated with related part in OO.o3.x.

Symphony help is based on Eclipse help mechanism. In the build, help content of OO.o 3.3 is used. But Symphony help content is avilable in source code package.

[[Category:Documentation]]

Symphony

2012-05-17T12:40:04Z

R4zoli: added paralell installation link

SUN Report Builder/Documentation

2011-05-26T07:55:50Z

R4zoli: /* Charts in report builder */

{{Documentation/Candidate}}

== Who Needs Reporting ==

You may be forgiven for thinking the sole purpose of reports is to provide nice-looking printouts of database records. A reporting engine provides essential tools for putting the data in a database for some practical use. Reports allow you to slice and view data in many different ways. As a freelancer, you can use reports to keep track of the time you spend on a particular project, view your earnings during a specified month, and see which customer brings you most work. Likewise, you can use reports to generate ready-to-send invoices. If you are learning a foreign language, then you can use reports to print a list of new words for a particular topic and keep track of your progress. You can also create a simple database to keep track of your achievements and generate a professionally-looking resume using a report. In other words, you can use reports for a wide variety of tasks.

== Why Sun Report Builder ==

Since OpenOffice.org comes with a built-in reporting feature you might wonder why you'd want to bolt another reporting engine on top of it. For starters, the built-in reporting capabilities can't be used for anything but the most simple reports. While the Report Wizard makes the process of creating a report rather straightforward, the default reporting tools are not very intuitive and not particularly flexible, which limits your ability to customize reports to your liking. The Sun Report Builder (SRB) is designed to overcome the shortcomings of the built-in reporting capabilities by adding a powerful reporting engine and a slew of nifty tools allownig you to create more advanced reports. The extension adds both advanced sorting and grouping capabilities as well as the ability to use SQL queries and functions in reports. More importantly, SRB makes it significantly easier to create a complex report layout via drag-and-drop. Further, SRB lets you insert charts in your reports.

== System Requirements ==

The SRB extension requires a fairly recent version of OpenOffice.org. Ideally, you should use the latest version of the productivity suite. Since SRB is written in Java, you should also check whether the Java Runtime Environment (JRE) software is installed on your machine and whether OpenOffice.org is configured to use it. To do this, choose Tools -> Options -> OpenOffice.org -> Java. Make sure the ''Use a Java runtime environment'' check box is ticked and a JRE is selected in the list of installed JREs. If this list is empty, then you have to install the JRE software which you can download from [http://www.java.com www.java.com].

== Installing Sun Report Builder ==

Since SRB is an OpenOffice.org extension, installing it on your machine is not particularly difficult. Download the latest version of SRB from [http://extensions.services.openoffice.org/project/reportdesign OpenOffice.org Extension Repository]. In OpenOffice.org, choose Tools -> Extension Manager. Press the Add button, select the downloaded .oxt file, and press Open. Restart OpenOffice.org (on Windows, you have to terminate Quicklauncher, too), and you are now ready.

== Getting Started with Sun Report Builder ==

The following make reference to SRB version 1.0.x.

The Sun Report Builder extension adds powerful reporting capabilities to OpenOffice.org Base and using it to create reports is easy, as we can see with a simple example. Suppose you're a freelance writer and you want to keep track of your submissions using a simple OpenOffice.org Base database that stores article titles, publications, submission dates, current status, and payment rates. This is a useful solution, but adding reporting capabilities turns the database into a handy analytical tool. With Sun Report Builder you can generate a list of articles grouped by publication showing article payment sums and charts for each publication.

To make it easier for you to follow the instructions below, I've added the submissions table and the Submissions_by_Publication report to the WriterDB.odb database. This database is part of the Writer's Tools extension which you can download [http://code.google.com/p/writertools/ here].

Once you have the database ready, open it in OpenOffice.org Base, switch to the Reports section, and click on the Create Report in Design View link. This opens the Report Designer window and before you start working on a report, let's take a closer look at Report Designer's essential components:

=== Sun Report Builder's Interface ===

[[Image:SRB_Diagram.png|thumb|375px|none|Sun Report Builder's Interface]]

'''A''' - The Report Controls toolbar contains buttons you can use to add fields, labels, graphics, and graphs to the report.

'''B''' - Main toolbar allows you to enable the Add Field, Report Navigator, and Sorting and Grouping palettes.

'''C''' - Align and Align at Section toolbar helps you align fields and other elements in the report.

'''D''' - The blank report page is divided into three default sections: Page Header, Detail, and Page Footer.

'''E''' - The Add Field palette allows you to quickly populate the report with fields by dragging them from the palette onto the report.

'''F''' - The Sorting and Grouping pallet can be used to group and sort the report's elements.

'''G''' - The Report Navigator lets you quickly locate and select a particular element in the report.

'''H''' - The Properties pane lets you specify the properties of the currently selected control. For example, if you select a field, then you can use the Properties pane to specify the field's data source and properties such as size, position, format, etc.

To create a report that groups all submissions by publication, you should add a new group header page section by selecting the Publication field from the Sorting and Grouping palette. Specify the desired sorting option (Ascending or Descending) and select Present from the Group Header drop-down list. Use the Add Field palette to place the Publication field inside the Publication Header section. You can then use the available formatting options under the General tab in the Properties pane to format the field to your liking. The Detail section of the page is designed to generate a list of database records. In our case the list will contain records related to a particular publication. Using the Add Field palette, add the desired fields (e.g., Title, Submission Date, and Payment) to the Details section. Aligning fields and labels in the reports can be a bit tricky, but the Align and Align at Section toolbar contains buttons that help. You can preview the report by pressing the Execute Report button in the Main toolbar to generate a list of all submissions grouped by publication.

Although you can use the created report as it is, you can do a few other things to make it even more useful. For example, you might want to add a field that calculates the sum of payments for each publication as well as the grand total. Let's start with the latter. Click on the Text Box button in the Report Controls toolbar and draw a field in the Page Footer section. In The Properties pane, switch to the Data tab and select the options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Report

To add a field that displays the sum of payments for each publication, you first need to enable the Group Footer page section. Select Present from the Group Footer drop-down list in the Sorting and Grouping palette. Draw then a field in the added Publication Footer and specify the field's options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Group: Publication

You can also add a graph that displays payments by publication. To do this, you first need to create a query that pulls data for the graph. Close the report, switch to the Queries section, and click on the Create Query in Design View link to create a new query. Select the table containing submission data and add the Publication and Payment fields to the query. From the Function drop-down list, select Group in the Publication column and Sum in the Payment column. Save the created query and open the report for editing. Click on the Graph button in the Main toolbar, and draw a graph in the Page Footer section. In the Properties pane, switch to the Data tab and select Query from the Content type drop-down list and the created query from the Content list.

If you don't fancy the default column graph, then you can tweak its properties by double-clicking on the graph to enter editing mode. Here you can specify different settings using the right-click context menu. For example, by using the Chart Type menu item you can change the default column chart to pie chart and add a 3-D look to it.
As you can see, creating reports with Sun Report Builder is straightforward. Once you've mastered the basics, you can use the reporting capabilities to make sense of the data stored in OpenOffice.org Base.

----
----

== Viewing the Report Navigator in Sun Report Builder ==
Let's identify a few key components of the SRB as seen in the Report Navigator. The Report Navigator is accessed under the View pull-down menu. To view the properties window, toggle it to be displayed under the View pull-down menu. The extended tips identify a lot of information about the components. To view the extended tips, toggle it to be displayed under the Help pull-down menu. The text below supplements the extended tips of your particular SRB version. Further, context help is available for various dialoges by pressing F1.

=== Report Navigator -> Report ===
Shows the various options for the report as a whole. These are different than the various options of individual components of the report. For example, if you use a filter on the report as a whole, then don't expect to perform functions on values you just filtered out.

==== Report Navigator -> Report -> Properties of General Tab ====
This controls the layout and presentation of the report.
* Name: The name of your report can be most anything of your choosing.
* Page Header:
* Page Footer:
* Print repeated values: You may not want repeated values printed for every report.

==== Report Navigator -> Report -> Properties of Data Tab ====
This controls the data from the database that is displayed in the report.
* Content Type: Can be Table, Query, or SQL command
* Content: Values dependent upon Content Type above.
* Analyze SQL command: Whether to allow the SQL command to be analyzed.
* Filter: The SQL filter command to perform on the database data

==== Report Navigator -> Report -> Functions ====
This controls the functions calculated in the report using OpenFormula. Generally all functions which are defined in the [http://wiki.oasis-open.org/office/About_OpenFormula OpenFormula] should be supported. But this is currently still ongoing work and may change after each release of the Sun Report Builder.

===== Report Navigator -> Report -> Functions -> Function -> Properties of General Tab =====
A function allows the user to perform calculations (see Supported Functions section) on the database data and display the results. Functions can either be in the global context of the report itself or in any group (see Groups section below). Functions are created using View -> Report Navigator -> Report -> Function. Right-click on Function and select New Function. Once you have selected your new function, in the context menu on the functions entry you can customize your function.
* Name: The name of your function can be most anything of your choosing.
* Formula: See Function Example below
* Initial value: See Function Example below
* Deep Traversing:
* Pre evaluation: You may not want the function to be evaluated until the report is finished.

==== Report Navigator -> Report -> Page Header -> Properties of General Tab ====
This controls the header on each page of the report. In a multi-page report, this can show at the top of each page. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Visible:
* Height:
* Conditional Print Expression: A conditional print expression allows the user to specify whether an element or section should or should not be visible when executing the report. If the print expression evaluates to true, then the element will be printed in the report. The syntax is the same as for functions.
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Header -> Properties of General Tab ====
This controls the header of the report. In a multi-page report, this will show only once at top of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Force New Page: Whether the current section and/or the next section is printed on a new page
* Keep Together: If the current section doesn't completely fit on a page, then print it on the next page
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Groups -> Sorting and Grouping Window ====
This controls whether and how you are grouping together database data. You can insert a data grouping into the report by using View -> Sorting and Grouping. It details on which fields, what sort order, what conditions, etc. you will be grouping your data. For more details, please see [http://dba.openoffice.org/specifications/ReportDesigner.odt this].
* Field/Expression: Either the field from the database or the expression. An example of an expressions might be to give the user the possibility to do arithmetic calculations with the value of other expressions as well as with the value of columns. (The actual implementation is part of 4.1 expression engine.)

* Sorting: Ascending or descending
* Group Header: Either show or hide
* Group Footer: Either show or hide
* Group On: What the data is grouped on depends upon the type of data chosen in Field/Expression
* Group Interval: This also depends upon the type of data chosen in Field/Expression
* Keep Together:

===== Report Navigator -> Report -> Groups -> <GroupingName> -> Properties of General Tab =====
This controls the visual presentation of your groupings.
* Keep Together:
* Start New Column: (In future releases, multiple columns will be available from the menu Format -> Page)
* Reset Page Number:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Functions -> Function -> Properties of General Tab ======
This allows you to perform calculations (see Supported Functions section) on the data groups and display the results. Again, functions are created by right-clicking on Function and select New Function.
* Name:
* Formula: Input using the OpenFormula syntax
* Initial Value: The initial evaluation value of the OpenFormula above
* Deep Traversing:
* Pre Evaluation:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Group Header -> Properties of General Tab ======
This controls under which condition the group header is displayed as well as many other attributes of the group header.
* Name:
* Force New Page:
* Keep Together:
* Repeat Section:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Detail -> Properties of General Tab ====
This controls the details of the report. It is the main body of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Undoubtedly, this section contains the database data you want pulled in your report.
* Name:
* Force New Page:
* Keep Together:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Footer -> Properties of General Tab ====
This compliments the Report Header section and contains the same components as the Report Header.

==== Report Navigator -> Report -> Page Footer -> Properties of General Tab ====
This compliments the Page Header section and contains the same components as the Page Header.

----
----

== Common components in any section ==
In each of the above sections you can have commonly-used data components from the Report Controls toolbar that make good use of the report. They are as follows:

=== Report Controls Toolbar -> Label Field -> Properties of General Tab ===
* Name:
* Label:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* (Horizontal) Alignment:
* Vertical Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Formatting:
* (Horizontal) Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of Data Tab ===
* Data Field Type: The kind of data (Field or formula, Function, Counter, User Defined Function)
* Data Field: The columns/fields of the report source
* Function: Such as Sum, Minimum, Maximum
* Scope: Contains all names of all groups. This includes the group where this control is contained in as well as the report itself as top level scope.
See [http://dba.openoffice.org/specifications/Function_Property_Browser.odt here] for more details.

=== Report Controls Toolbar -> Image Control -> Properties of General Tab ===
* Name:
* Preserve as link:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Graphics:
* Scale:

=== Report Controls Toolbar -> Image Control -> Properties of Data Tab ===
* Data Field Type:
* Data Field:
* Function:
* Scope:

=== Report Controls Toolbar -> Chart/Shape -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Font:
* Chart Type:
* Preview Rows:

=== Report Controls Toolbar -> Chart/Shape -> Properties of Data Tab ===
* Content Type:
* Content:
* Analyze SQL Command:
* Filter:
* Sort:
* Link Master Fields:
* Link Slave Fields:

=== Report Controls Toolbar -> Fixed Line -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Orientation:

----
----

== Syntax ==
* quote for [ is \
* \\
* [] as reference for formula or field name
* "" to quote strings
* . as decimal separator
* date as in java specific
* parameter separator is ; (semicolon) and it is allowed to let some parameters empty inside a call like XYZ(;kk;;kkb)

----
----

== Functions ==
The current Sun Report Builder (verson 1.0.x) includes functions in the following categories:

'''Datetime''' 
DATE, DATEDIF, DATEVALUE, DAY, DAYS, HOUR, MINUTE, MONTH, NOW, SECOND, TIME, TIMEVALUE, TODAY, WEEKDAY, YEAR

'''Financial''' 
Financial

'''Information''' 
CHOOSE, COUNT, COUNTA, COUNTBLANK, HASCHANGED, ISBLANK, ISERR, ISERROR, ISEVEN, ISLOGICAL, ISNA, ISNONTEXT, ISNUMBER, ISODD, ISREF, ISTEXT, NA

'''Logical''' 
AND, FALSE, IF, NOT, OR, TRUE, XOR

'''Math''' 
ABS, AVERAGE, EVEN, MAX, MAXA, MIN, MINA, MOD, ODD, SUM

'''Rounding''' 
INT

'''Text''' 
EXACT, FIND, LEFT, LEN, LOWER, MID, REPLACE, REPT, RIGHT, SUBSTITUTE, T, TEXT, TRIM, UNICHAR, UNICODE, UPPER, URLENCODE

'''Userdefined''' 
NULL

A detailed explanation of the above functions will be found [[Base/Reports/Functions|here.]]
Additional details and code can be found [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Functions here].

CONCAT or CONCATENATE functions not supported, but you can use [Textfieldname]&" "&[Textfieldname] to concatenate text fields, not forget to format it as text.

Please note that these functions are specific to the SRB. Additional functionality may be obtained from the database backend capabilities. For example, if you are using OpenOffice.org's native HSQL database, then you may also use HSQL functions and stored procedures along with OpenOffice.org's queries to generate a wide variety of information shown in reports.

----
----

== Examples ==
=== Function Example ===
The illustration below shows how subtotal fields are created in Report Builder, using functions:

[[Image:SumFieldInReportBuilder.jpg]]

The report source table is shown on the upper left.

The resulting report layout is illustrated below the table. A group has been defined on the plProductType field. The sum field is created on the group footer. The rightmost part of the image shows the definition of a function that serves as the data source for the sum field.

=== Query Example ===
The URL below shows how to use queries in Report Builder:

See [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Example here].

=== Computed Fields Example ===
Computed fields can be created in the way that the formula is entered directly into the data field.

E.g. 100*[Population]/[PopulationCount] to get the percentage of the current population
== Charts in report builder ==
You can insert Chart into report builder report, into any places, but only some has a good reason to do.

Not wise to add to details section, it is for single data output, the headers and footer the right place for charts where you print summarized data, and chart for explaining data series, trends, etc.

Open report for edit, and insert Chart into Group/Page/Report header/footer.

When you inserted it shows columns chart as default, now needs to bound to some data source, Select Table/Query/SQL commands. When you selected, the chart shows data what can retrieve from data source.

When you decide to use chart in report useful to create query, which contain only that data what you want to show in that place, without excessive data, because you can not remove them with data ranges dialog as you can do in Calc.

The Charts in report builder has bunch of limitations:

The “First row as label” grayed out and as default selected the data source field names (or aliases names), this is not changeable in through UI in report builder. For this reason I suggest to use query or SQL commands as report/chart source not a Table.

[[Image:Report chart data ranges.PNG]]

The first field data (column in Calc and in Chart) in table or query, can be used as categories, by selecting “First column as label ”.

The field names bounded to the places in table, the counting starts from 0, the first field is 0.

The first field name presented as “label 0”, the second field name is“label1”, … etc.

[[Image:Report chart dataseries labels.PNG]]

You can not select data series interactively, only can remove whole data series from chart. The data series range not changeable, it contain whole data in table/query, and it has an ugly name “0”, “1”, … etc., which you can see in data series window.

[[Image:Report chart dataseries ranges.PNG]]

The Categories not changeable, it is hard coded to data fields.

== Extensions ==
=== EuroOffice Map Chart ===
One extension further extends the functionality of Sun Report Builder. A detailed description of its use together with the basic steps of creating your first report can be found [http://www.multiracio.com/eurooffice/support/tutorials/eurooffice-map-chart-tutorials/how-to-use-map-charts-with-sun-report-builder here]. This tutorial goes from creating your first report to defining a quite complicated new function, so it can be a useful resource for beginners and advanced users alike (not just for those looking for a way to create map charts).

[[Category:Sun Report Builder]]
[[Category: Base Documentation]]

[[ru:RU/SUN Report Builder/Documentation]]

SUN Report Builder/Documentation

2011-05-26T07:49:16Z

R4zoli:

{{Documentation/Candidate}}

== Who Needs Reporting ==

You may be forgiven for thinking the sole purpose of reports is to provide nice-looking printouts of database records. A reporting engine provides essential tools for putting the data in a database for some practical use. Reports allow you to slice and view data in many different ways. As a freelancer, you can use reports to keep track of the time you spend on a particular project, view your earnings during a specified month, and see which customer brings you most work. Likewise, you can use reports to generate ready-to-send invoices. If you are learning a foreign language, then you can use reports to print a list of new words for a particular topic and keep track of your progress. You can also create a simple database to keep track of your achievements and generate a professionally-looking resume using a report. In other words, you can use reports for a wide variety of tasks.

== Why Sun Report Builder ==

Since OpenOffice.org comes with a built-in reporting feature you might wonder why you'd want to bolt another reporting engine on top of it. For starters, the built-in reporting capabilities can't be used for anything but the most simple reports. While the Report Wizard makes the process of creating a report rather straightforward, the default reporting tools are not very intuitive and not particularly flexible, which limits your ability to customize reports to your liking. The Sun Report Builder (SRB) is designed to overcome the shortcomings of the built-in reporting capabilities by adding a powerful reporting engine and a slew of nifty tools allownig you to create more advanced reports. The extension adds both advanced sorting and grouping capabilities as well as the ability to use SQL queries and functions in reports. More importantly, SRB makes it significantly easier to create a complex report layout via drag-and-drop. Further, SRB lets you insert charts in your reports.

== System Requirements ==

The SRB extension requires a fairly recent version of OpenOffice.org. Ideally, you should use the latest version of the productivity suite. Since SRB is written in Java, you should also check whether the Java Runtime Environment (JRE) software is installed on your machine and whether OpenOffice.org is configured to use it. To do this, choose Tools -> Options -> OpenOffice.org -> Java. Make sure the ''Use a Java runtime environment'' check box is ticked and a JRE is selected in the list of installed JREs. If this list is empty, then you have to install the JRE software which you can download from [http://www.java.com www.java.com].

== Installing Sun Report Builder ==

Since SRB is an OpenOffice.org extension, installing it on your machine is not particularly difficult. Download the latest version of SRB from [http://extensions.services.openoffice.org/project/reportdesign OpenOffice.org Extension Repository]. In OpenOffice.org, choose Tools -> Extension Manager. Press the Add button, select the downloaded .oxt file, and press Open. Restart OpenOffice.org (on Windows, you have to terminate Quicklauncher, too), and you are now ready.

== Getting Started with Sun Report Builder ==

The following make reference to SRB version 1.0.x.

The Sun Report Builder extension adds powerful reporting capabilities to OpenOffice.org Base and using it to create reports is easy, as we can see with a simple example. Suppose you're a freelance writer and you want to keep track of your submissions using a simple OpenOffice.org Base database that stores article titles, publications, submission dates, current status, and payment rates. This is a useful solution, but adding reporting capabilities turns the database into a handy analytical tool. With Sun Report Builder you can generate a list of articles grouped by publication showing article payment sums and charts for each publication.

To make it easier for you to follow the instructions below, I've added the submissions table and the Submissions_by_Publication report to the WriterDB.odb database. This database is part of the Writer's Tools extension which you can download [http://code.google.com/p/writertools/ here].

Once you have the database ready, open it in OpenOffice.org Base, switch to the Reports section, and click on the Create Report in Design View link. This opens the Report Designer window and before you start working on a report, let's take a closer look at Report Designer's essential components:

=== Sun Report Builder's Interface ===

[[Image:SRB_Diagram.png|thumb|375px|none|Sun Report Builder's Interface]]

'''A''' - The Report Controls toolbar contains buttons you can use to add fields, labels, graphics, and graphs to the report.

'''B''' - Main toolbar allows you to enable the Add Field, Report Navigator, and Sorting and Grouping palettes.

'''C''' - Align and Align at Section toolbar helps you align fields and other elements in the report.

'''D''' - The blank report page is divided into three default sections: Page Header, Detail, and Page Footer.

'''E''' - The Add Field palette allows you to quickly populate the report with fields by dragging them from the palette onto the report.

'''F''' - The Sorting and Grouping pallet can be used to group and sort the report's elements.

'''G''' - The Report Navigator lets you quickly locate and select a particular element in the report.

'''H''' - The Properties pane lets you specify the properties of the currently selected control. For example, if you select a field, then you can use the Properties pane to specify the field's data source and properties such as size, position, format, etc.

To create a report that groups all submissions by publication, you should add a new group header page section by selecting the Publication field from the Sorting and Grouping palette. Specify the desired sorting option (Ascending or Descending) and select Present from the Group Header drop-down list. Use the Add Field palette to place the Publication field inside the Publication Header section. You can then use the available formatting options under the General tab in the Properties pane to format the field to your liking. The Detail section of the page is designed to generate a list of database records. In our case the list will contain records related to a particular publication. Using the Add Field palette, add the desired fields (e.g., Title, Submission Date, and Payment) to the Details section. Aligning fields and labels in the reports can be a bit tricky, but the Align and Align at Section toolbar contains buttons that help. You can preview the report by pressing the Execute Report button in the Main toolbar to generate a list of all submissions grouped by publication.

Although you can use the created report as it is, you can do a few other things to make it even more useful. For example, you might want to add a field that calculates the sum of payments for each publication as well as the grand total. Let's start with the latter. Click on the Text Box button in the Report Controls toolbar and draw a field in the Page Footer section. In The Properties pane, switch to the Data tab and select the options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Report

To add a field that displays the sum of payments for each publication, you first need to enable the Group Footer page section. Select Present from the Group Footer drop-down list in the Sorting and Grouping palette. Draw then a field in the added Publication Footer and specify the field's options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Group: Publication

You can also add a graph that displays payments by publication. To do this, you first need to create a query that pulls data for the graph. Close the report, switch to the Queries section, and click on the Create Query in Design View link to create a new query. Select the table containing submission data and add the Publication and Payment fields to the query. From the Function drop-down list, select Group in the Publication column and Sum in the Payment column. Save the created query and open the report for editing. Click on the Graph button in the Main toolbar, and draw a graph in the Page Footer section. In the Properties pane, switch to the Data tab and select Query from the Content type drop-down list and the created query from the Content list.

If you don't fancy the default column graph, then you can tweak its properties by double-clicking on the graph to enter editing mode. Here you can specify different settings using the right-click context menu. For example, by using the Chart Type menu item you can change the default column chart to pie chart and add a 3-D look to it.
As you can see, creating reports with Sun Report Builder is straightforward. Once you've mastered the basics, you can use the reporting capabilities to make sense of the data stored in OpenOffice.org Base.

----
----

== Viewing the Report Navigator in Sun Report Builder ==
Let's identify a few key components of the SRB as seen in the Report Navigator. The Report Navigator is accessed under the View pull-down menu. To view the properties window, toggle it to be displayed under the View pull-down menu. The extended tips identify a lot of information about the components. To view the extended tips, toggle it to be displayed under the Help pull-down menu. The text below supplements the extended tips of your particular SRB version. Further, context help is available for various dialoges by pressing F1.

=== Report Navigator -> Report ===
Shows the various options for the report as a whole. These are different than the various options of individual components of the report. For example, if you use a filter on the report as a whole, then don't expect to perform functions on values you just filtered out.

==== Report Navigator -> Report -> Properties of General Tab ====
This controls the layout and presentation of the report.
* Name: The name of your report can be most anything of your choosing.
* Page Header:
* Page Footer:
* Print repeated values: You may not want repeated values printed for every report.

==== Report Navigator -> Report -> Properties of Data Tab ====
This controls the data from the database that is displayed in the report.
* Content Type: Can be Table, Query, or SQL command
* Content: Values dependent upon Content Type above.
* Analyze SQL command: Whether to allow the SQL command to be analyzed.
* Filter: The SQL filter command to perform on the database data

==== Report Navigator -> Report -> Functions ====
This controls the functions calculated in the report using OpenFormula. Generally all functions which are defined in the [http://wiki.oasis-open.org/office/About_OpenFormula OpenFormula] should be supported. But this is currently still ongoing work and may change after each release of the Sun Report Builder.

===== Report Navigator -> Report -> Functions -> Function -> Properties of General Tab =====
A function allows the user to perform calculations (see Supported Functions section) on the database data and display the results. Functions can either be in the global context of the report itself or in any group (see Groups section below). Functions are created using View -> Report Navigator -> Report -> Function. Right-click on Function and select New Function. Once you have selected your new function, in the context menu on the functions entry you can customize your function.
* Name: The name of your function can be most anything of your choosing.
* Formula: See Function Example below
* Initial value: See Function Example below
* Deep Traversing:
* Pre evaluation: You may not want the function to be evaluated until the report is finished.

==== Report Navigator -> Report -> Page Header -> Properties of General Tab ====
This controls the header on each page of the report. In a multi-page report, this can show at the top of each page. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Visible:
* Height:
* Conditional Print Expression: A conditional print expression allows the user to specify whether an element or section should or should not be visible when executing the report. If the print expression evaluates to true, then the element will be printed in the report. The syntax is the same as for functions.
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Header -> Properties of General Tab ====
This controls the header of the report. In a multi-page report, this will show only once at top of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Force New Page: Whether the current section and/or the next section is printed on a new page
* Keep Together: If the current section doesn't completely fit on a page, then print it on the next page
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Groups -> Sorting and Grouping Window ====
This controls whether and how you are grouping together database data. You can insert a data grouping into the report by using View -> Sorting and Grouping. It details on which fields, what sort order, what conditions, etc. you will be grouping your data. For more details, please see [http://dba.openoffice.org/specifications/ReportDesigner.odt this].
* Field/Expression: Either the field from the database or the expression. An example of an expressions might be to give the user the possibility to do arithmetic calculations with the value of other expressions as well as with the value of columns. (The actual implementation is part of 4.1 expression engine.)

* Sorting: Ascending or descending
* Group Header: Either show or hide
* Group Footer: Either show or hide
* Group On: What the data is grouped on depends upon the type of data chosen in Field/Expression
* Group Interval: This also depends upon the type of data chosen in Field/Expression
* Keep Together:

===== Report Navigator -> Report -> Groups -> <GroupingName> -> Properties of General Tab =====
This controls the visual presentation of your groupings.
* Keep Together:
* Start New Column: (In future releases, multiple columns will be available from the menu Format -> Page)
* Reset Page Number:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Functions -> Function -> Properties of General Tab ======
This allows you to perform calculations (see Supported Functions section) on the data groups and display the results. Again, functions are created by right-clicking on Function and select New Function.
* Name:
* Formula: Input using the OpenFormula syntax
* Initial Value: The initial evaluation value of the OpenFormula above
* Deep Traversing:
* Pre Evaluation:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Group Header -> Properties of General Tab ======
This controls under which condition the group header is displayed as well as many other attributes of the group header.
* Name:
* Force New Page:
* Keep Together:
* Repeat Section:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Detail -> Properties of General Tab ====
This controls the details of the report. It is the main body of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Undoubtedly, this section contains the database data you want pulled in your report.
* Name:
* Force New Page:
* Keep Together:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Footer -> Properties of General Tab ====
This compliments the Report Header section and contains the same components as the Report Header.

==== Report Navigator -> Report -> Page Footer -> Properties of General Tab ====
This compliments the Page Header section and contains the same components as the Page Header.

----
----

== Common components in any section ==
In each of the above sections you can have commonly-used data components from the Report Controls toolbar that make good use of the report. They are as follows:

=== Report Controls Toolbar -> Label Field -> Properties of General Tab ===
* Name:
* Label:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* (Horizontal) Alignment:
* Vertical Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Formatting:
* (Horizontal) Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of Data Tab ===
* Data Field Type: The kind of data (Field or formula, Function, Counter, User Defined Function)
* Data Field: The columns/fields of the report source
* Function: Such as Sum, Minimum, Maximum
* Scope: Contains all names of all groups. This includes the group where this control is contained in as well as the report itself as top level scope.
See [http://dba.openoffice.org/specifications/Function_Property_Browser.odt here] for more details.

=== Report Controls Toolbar -> Image Control -> Properties of General Tab ===
* Name:
* Preserve as link:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Graphics:
* Scale:

=== Report Controls Toolbar -> Image Control -> Properties of Data Tab ===
* Data Field Type:
* Data Field:
* Function:
* Scope:

=== Report Controls Toolbar -> Chart/Shape -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Font:
* Chart Type:
* Preview Rows:

=== Report Controls Toolbar -> Chart/Shape -> Properties of Data Tab ===
* Content Type:
* Content:
* Analyze SQL Command:
* Filter:
* Sort:
* Link Master Fields:
* Link Slave Fields:

=== Report Controls Toolbar -> Fixed Line -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Orientation:

----
----

== Syntax ==
* quote for [ is \
* \\
* [] as reference for formula or field name
* "" to quote strings
* . as decimal separator
* date as in java specific
* parameter separator is ; (semicolon) and it is allowed to let some parameters empty inside a call like XYZ(;kk;;kkb)

----
----

== Functions ==
The current Sun Report Builder (verson 1.0.x) includes functions in the following categories:

'''Datetime''' 
DATE, DATEDIF, DATEVALUE, DAY, DAYS, HOUR, MINUTE, MONTH, NOW, SECOND, TIME, TIMEVALUE, TODAY, WEEKDAY, YEAR

'''Financial''' 
Financial

'''Information''' 
CHOOSE, COUNT, COUNTA, COUNTBLANK, HASCHANGED, ISBLANK, ISERR, ISERROR, ISEVEN, ISLOGICAL, ISNA, ISNONTEXT, ISNUMBER, ISODD, ISREF, ISTEXT, NA

'''Logical''' 
AND, FALSE, IF, NOT, OR, TRUE, XOR

'''Math''' 
ABS, AVERAGE, EVEN, MAX, MAXA, MIN, MINA, MOD, ODD, SUM

'''Rounding''' 
INT

'''Text''' 
EXACT, FIND, LEFT, LEN, LOWER, MID, REPLACE, REPT, RIGHT, SUBSTITUTE, T, TEXT, TRIM, UNICHAR, UNICODE, UPPER, URLENCODE

'''Userdefined''' 
NULL

A detailed explanation of the above functions will be found [[Base/Reports/Functions|here.]]
Additional details and code can be found [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Functions here].

CONCAT or CONCATENATE functions not supported, but you can use [Textfieldname]&" "&[Textfieldname] to concatenate text fields, not forget to format it as text.

Please note that these functions are specific to the SRB. Additional functionality may be obtained from the database backend capabilities. For example, if you are using OpenOffice.org's native HSQL database, then you may also use HSQL functions and stored procedures along with OpenOffice.org's queries to generate a wide variety of information shown in reports.

----
----

== Examples ==
=== Function Example ===
The illustration below shows how subtotal fields are created in Report Builder, using functions:

[[Image:SumFieldInReportBuilder.jpg]]

The report source table is shown on the upper left.

The resulting report layout is illustrated below the table. A group has been defined on the plProductType field. The sum field is created on the group footer. The rightmost part of the image shows the definition of a function that serves as the data source for the sum field.

=== Query Example ===
The URL below shows how to use queries in Report Builder:

See [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Example here].

=== Computed Fields Example ===
Computed fields can be created in the way that the formula is entered directly into the data field.

E.g. 100*[Population]/[PopulationCount] to get the percentage of the current population
= Charts in report builder =
You can insert Chart into report builder report, into any places, but only some has a good reason to do.

Not wise to add to details section, it is for single data output, the headers and footer the right place for charts where you print summarized data, and chart for explaining data series, trends, etc.

Open report for edit, and insert Chart into Group/Page/Report header/footer.

When you inserted it shows columns chart as default, now needs to bound to some data source, Select Table/Query/SQL commands. When you selected, the chart shows data what can retrieve from data source.

When you decide to use chart in report useful to create query, which contain only that data what you want to show in that place, without excessive data, because you can not remove them with data ranges dialog as you can do in Calc.

The Charts in report builder has bunch of limitations:

The “First row as label” grayed out and as default selected the data source field names (or aliases names), this is not changeable in through UI in report builder. For this reason I suggest to use query or SQL commands as report/chart source not a Table.

[[Image:Report chart data ranges.PNG]]

The first field data (column in Calc and in Chart) in table or query, can be used as categories, by selecting “First column as label ”.

The field names bounded to the places in table, the counting starts from 0, the first field is 0.

The first field name presented as “label 0”, the second field name is“label1”, … etc.

[[Image:Report chart dataseries labels.PNG]]

You can not select data series interactively, only can remove whole data series from chart. The data series range not changeable, it contain whole data in table/query, and it has an ugly name “0”, “1”, … etc., which you can see in data series window.

[[Image:Report chart dataseries ranges.PNG]]

The Categories not changeable, it is hard coded to data fields.

== Extensions ==
=== EuroOffice Map Chart ===
One extension further extends the functionality of Sun Report Builder. A detailed description of its use together with the basic steps of creating your first report can be found [http://www.multiracio.com/eurooffice/support/tutorials/eurooffice-map-chart-tutorials/how-to-use-map-charts-with-sun-report-builder here]. This tutorial goes from creating your first report to defining a quite complicated new function, so it can be a useful resource for beginners and advanced users alike (not just for those looking for a way to create map charts).

[[Category:Sun Report Builder]]
[[Category: Base Documentation]]

[[ru:RU/SUN Report Builder/Documentation]]

File:Report chart dataseries ranges.PNG

2011-05-26T07:48:18Z

R4zoli:

File:Report chart dataseries labels.PNG

2011-05-26T07:47:35Z

R4zoli:

File:Report chart data ranges.PNG

2011-05-26T07:45:19Z

R4zoli:

SUN Report Builder/Documentation

2011-05-26T07:40:25Z

R4zoli: /* Computed Fields Example */ (checkpoint save)

{{Documentation/Candidate}}

== Who Needs Reporting ==

You may be forgiven for thinking the sole purpose of reports is to provide nice-looking printouts of database records. A reporting engine provides essential tools for putting the data in a database for some practical use. Reports allow you to slice and view data in many different ways. As a freelancer, you can use reports to keep track of the time you spend on a particular project, view your earnings during a specified month, and see which customer brings you most work. Likewise, you can use reports to generate ready-to-send invoices. If you are learning a foreign language, then you can use reports to print a list of new words for a particular topic and keep track of your progress. You can also create a simple database to keep track of your achievements and generate a professionally-looking resume using a report. In other words, you can use reports for a wide variety of tasks.

== Why Sun Report Builder ==

Since OpenOffice.org comes with a built-in reporting feature you might wonder why you'd want to bolt another reporting engine on top of it. For starters, the built-in reporting capabilities can't be used for anything but the most simple reports. While the Report Wizard makes the process of creating a report rather straightforward, the default reporting tools are not very intuitive and not particularly flexible, which limits your ability to customize reports to your liking. The Sun Report Builder (SRB) is designed to overcome the shortcomings of the built-in reporting capabilities by adding a powerful reporting engine and a slew of nifty tools allownig you to create more advanced reports. The extension adds both advanced sorting and grouping capabilities as well as the ability to use SQL queries and functions in reports. More importantly, SRB makes it significantly easier to create a complex report layout via drag-and-drop. Further, SRB lets you insert charts in your reports.

== System Requirements ==

The SRB extension requires a fairly recent version of OpenOffice.org. Ideally, you should use the latest version of the productivity suite. Since SRB is written in Java, you should also check whether the Java Runtime Environment (JRE) software is installed on your machine and whether OpenOffice.org is configured to use it. To do this, choose Tools -> Options -> OpenOffice.org -> Java. Make sure the ''Use a Java runtime environment'' check box is ticked and a JRE is selected in the list of installed JREs. If this list is empty, then you have to install the JRE software which you can download from [http://www.java.com www.java.com].

== Installing Sun Report Builder ==

Since SRB is an OpenOffice.org extension, installing it on your machine is not particularly difficult. Download the latest version of SRB from [http://extensions.services.openoffice.org/project/reportdesign OpenOffice.org Extension Repository]. In OpenOffice.org, choose Tools -> Extension Manager. Press the Add button, select the downloaded .oxt file, and press Open. Restart OpenOffice.org (on Windows, you have to terminate Quicklauncher, too), and you are now ready.

== Getting Started with Sun Report Builder ==

The following make reference to SRB version 1.0.x.

The Sun Report Builder extension adds powerful reporting capabilities to OpenOffice.org Base and using it to create reports is easy, as we can see with a simple example. Suppose you're a freelance writer and you want to keep track of your submissions using a simple OpenOffice.org Base database that stores article titles, publications, submission dates, current status, and payment rates. This is a useful solution, but adding reporting capabilities turns the database into a handy analytical tool. With Sun Report Builder you can generate a list of articles grouped by publication showing article payment sums and charts for each publication.

To make it easier for you to follow the instructions below, I've added the submissions table and the Submissions_by_Publication report to the WriterDB.odb database. This database is part of the Writer's Tools extension which you can download [http://code.google.com/p/writertools/ here].

Once you have the database ready, open it in OpenOffice.org Base, switch to the Reports section, and click on the Create Report in Design View link. This opens the Report Designer window and before you start working on a report, let's take a closer look at Report Designer's essential components:

=== Sun Report Builder's Interface ===

[[Image:SRB_Diagram.png|thumb|375px|none|Sun Report Builder's Interface]]

'''A''' - The Report Controls toolbar contains buttons you can use to add fields, labels, graphics, and graphs to the report.

'''B''' - Main toolbar allows you to enable the Add Field, Report Navigator, and Sorting and Grouping palettes.

'''C''' - Align and Align at Section toolbar helps you align fields and other elements in the report.

'''D''' - The blank report page is divided into three default sections: Page Header, Detail, and Page Footer.

'''E''' - The Add Field palette allows you to quickly populate the report with fields by dragging them from the palette onto the report.

'''F''' - The Sorting and Grouping pallet can be used to group and sort the report's elements.

'''G''' - The Report Navigator lets you quickly locate and select a particular element in the report.

'''H''' - The Properties pane lets you specify the properties of the currently selected control. For example, if you select a field, then you can use the Properties pane to specify the field's data source and properties such as size, position, format, etc.

To create a report that groups all submissions by publication, you should add a new group header page section by selecting the Publication field from the Sorting and Grouping palette. Specify the desired sorting option (Ascending or Descending) and select Present from the Group Header drop-down list. Use the Add Field palette to place the Publication field inside the Publication Header section. You can then use the available formatting options under the General tab in the Properties pane to format the field to your liking. The Detail section of the page is designed to generate a list of database records. In our case the list will contain records related to a particular publication. Using the Add Field palette, add the desired fields (e.g., Title, Submission Date, and Payment) to the Details section. Aligning fields and labels in the reports can be a bit tricky, but the Align and Align at Section toolbar contains buttons that help. You can preview the report by pressing the Execute Report button in the Main toolbar to generate a list of all submissions grouped by publication.

Although you can use the created report as it is, you can do a few other things to make it even more useful. For example, you might want to add a field that calculates the sum of payments for each publication as well as the grand total. Let's start with the latter. Click on the Text Box button in the Report Controls toolbar and draw a field in the Page Footer section. In The Properties pane, switch to the Data tab and select the options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Report

To add a field that displays the sum of payments for each publication, you first need to enable the Group Footer page section. Select Present from the Group Footer drop-down list in the Sorting and Grouping palette. Draw then a field in the added Publication Footer and specify the field's options as follows:

* Data Field Type: Function
* Data field: Payment
* Function: Accumulation
* Scope: Group: Publication

You can also add a graph that displays payments by publication. To do this, you first need to create a query that pulls data for the graph. Close the report, switch to the Queries section, and click on the Create Query in Design View link to create a new query. Select the table containing submission data and add the Publication and Payment fields to the query. From the Function drop-down list, select Group in the Publication column and Sum in the Payment column. Save the created query and open the report for editing. Click on the Graph button in the Main toolbar, and draw a graph in the Page Footer section. In the Properties pane, switch to the Data tab and select Query from the Content type drop-down list and the created query from the Content list.

If you don't fancy the default column graph, then you can tweak its properties by double-clicking on the graph to enter editing mode. Here you can specify different settings using the right-click context menu. For example, by using the Chart Type menu item you can change the default column chart to pie chart and add a 3-D look to it.
As you can see, creating reports with Sun Report Builder is straightforward. Once you've mastered the basics, you can use the reporting capabilities to make sense of the data stored in OpenOffice.org Base.

----
----

== Viewing the Report Navigator in Sun Report Builder ==
Let's identify a few key components of the SRB as seen in the Report Navigator. The Report Navigator is accessed under the View pull-down menu. To view the properties window, toggle it to be displayed under the View pull-down menu. The extended tips identify a lot of information about the components. To view the extended tips, toggle it to be displayed under the Help pull-down menu. The text below supplements the extended tips of your particular SRB version. Further, context help is available for various dialoges by pressing F1.

=== Report Navigator -> Report ===
Shows the various options for the report as a whole. These are different than the various options of individual components of the report. For example, if you use a filter on the report as a whole, then don't expect to perform functions on values you just filtered out.

==== Report Navigator -> Report -> Properties of General Tab ====
This controls the layout and presentation of the report.
* Name: The name of your report can be most anything of your choosing.
* Page Header:
* Page Footer:
* Print repeated values: You may not want repeated values printed for every report.

==== Report Navigator -> Report -> Properties of Data Tab ====
This controls the data from the database that is displayed in the report.
* Content Type: Can be Table, Query, or SQL command
* Content: Values dependent upon Content Type above.
* Analyze SQL command: Whether to allow the SQL command to be analyzed.
* Filter: The SQL filter command to perform on the database data

==== Report Navigator -> Report -> Functions ====
This controls the functions calculated in the report using OpenFormula. Generally all functions which are defined in the [http://wiki.oasis-open.org/office/About_OpenFormula OpenFormula] should be supported. But this is currently still ongoing work and may change after each release of the Sun Report Builder.

===== Report Navigator -> Report -> Functions -> Function -> Properties of General Tab =====
A function allows the user to perform calculations (see Supported Functions section) on the database data and display the results. Functions can either be in the global context of the report itself or in any group (see Groups section below). Functions are created using View -> Report Navigator -> Report -> Function. Right-click on Function and select New Function. Once you have selected your new function, in the context menu on the functions entry you can customize your function.
* Name: The name of your function can be most anything of your choosing.
* Formula: See Function Example below
* Initial value: See Function Example below
* Deep Traversing:
* Pre evaluation: You may not want the function to be evaluated until the report is finished.

==== Report Navigator -> Report -> Page Header -> Properties of General Tab ====
This controls the header on each page of the report. In a multi-page report, this can show at the top of each page. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Visible:
* Height:
* Conditional Print Expression: A conditional print expression allows the user to specify whether an element or section should or should not be visible when executing the report. If the print expression evaluates to true, then the element will be printed in the report. The syntax is the same as for functions.
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Header -> Properties of General Tab ====
This controls the header of the report. In a multi-page report, this will show only once at top of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Each of these components also have their respective components.
* Name:
* Force New Page: Whether the current section and/or the next section is printed on a new page
* Keep Together: If the current section doesn't completely fit on a page, then print it on the next page
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Groups -> Sorting and Grouping Window ====
This controls whether and how you are grouping together database data. You can insert a data grouping into the report by using View -> Sorting and Grouping. It details on which fields, what sort order, what conditions, etc. you will be grouping your data. For more details, please see [http://dba.openoffice.org/specifications/ReportDesigner.odt this].
* Field/Expression: Either the field from the database or the expression. An example of an expressions might be to give the user the possibility to do arithmetic calculations with the value of other expressions as well as with the value of columns. (The actual implementation is part of 4.1 expression engine.)

* Sorting: Ascending or descending
* Group Header: Either show or hide
* Group Footer: Either show or hide
* Group On: What the data is grouped on depends upon the type of data chosen in Field/Expression
* Group Interval: This also depends upon the type of data chosen in Field/Expression
* Keep Together:

===== Report Navigator -> Report -> Groups -> <GroupingName> -> Properties of General Tab =====
This controls the visual presentation of your groupings.
* Keep Together:
* Start New Column: (In future releases, multiple columns will be available from the menu Format -> Page)
* Reset Page Number:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Functions -> Function -> Properties of General Tab ======
This allows you to perform calculations (see Supported Functions section) on the data groups and display the results. Again, functions are created by right-clicking on Function and select New Function.
* Name:
* Formula: Input using the OpenFormula syntax
* Initial Value: The initial evaluation value of the OpenFormula above
* Deep Traversing:
* Pre Evaluation:

====== Report Navigator -> Report -> Groups -> <GroupingName> -> Group Header -> Properties of General Tab ======
This controls under which condition the group header is displayed as well as many other attributes of the group header.
* Name:
* Force New Page:
* Keep Together:
* Repeat Section:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Detail -> Properties of General Tab ====
This controls the details of the report. It is the main body of the report. It can contain other components such as text fields, text boxes, images controls, charts, lines, etc. Undoubtedly, this section contains the database data you want pulled in your report.
* Name:
* Force New Page:
* Keep Together:
* Visible:
* Height:
* Conditional Print Expression:
* Background Color:
* Background Transparent:

==== Report Navigator -> Report -> Report Footer -> Properties of General Tab ====
This compliments the Report Header section and contains the same components as the Report Header.

==== Report Navigator -> Report -> Page Footer -> Properties of General Tab ====
This compliments the Page Header section and contains the same components as the Page Header.

----
----

== Common components in any section ==
In each of the above sections you can have commonly-used data components from the Report Controls toolbar that make good use of the report. They are as follows:

=== Report Controls Toolbar -> Label Field -> Properties of General Tab ===
* Name:
* Label:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* (Horizontal) Alignment:
* Vertical Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Font:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Formatting:
* (Horizontal) Alignment:

=== Report Controls Toolbar -> Formatted Field -> Properties of Data Tab ===
* Data Field Type: The kind of data (Field or formula, Function, Counter, User Defined Function)
* Data Field: The columns/fields of the report source
* Function: Such as Sum, Minimum, Maximum
* Scope: Contains all names of all groups. This includes the group where this control is contained in as well as the report itself as top level scope.
See [http://dba.openoffice.org/specifications/Function_Property_Browser.odt here] for more details.

=== Report Controls Toolbar -> Image Control -> Properties of General Tab ===
* Name:
* Preserve as link:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Background Color:
* Background Transparent:
* Graphics:
* Scale:

=== Report Controls Toolbar -> Image Control -> Properties of Data Tab ===
* Data Field Type:
* Data Field:
* Function:
* Scope:

=== Report Controls Toolbar -> Chart/Shape -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Print Repeated Values:
* Conditional Print Expression:
* Print When Group Change:
* Font:
* Chart Type:
* Preview Rows:

=== Report Controls Toolbar -> Chart/Shape -> Properties of Data Tab ===
* Content Type:
* Content:
* Analyze SQL Command:
* Filter:
* Sort:
* Link Master Fields:
* Link Slave Fields:

=== Report Controls Toolbar -> Fixed Line -> Properties of General Tab ===
* Name:
* Position X:
* Position Y:
* Width:
* Height:
* Orientation:

----
----

== Syntax ==
* quote for [ is \
* \\
* [] as reference for formula or field name
* "" to quote strings
* . as decimal separator
* date as in java specific
* parameter separator is ; (semicolon) and it is allowed to let some parameters empty inside a call like XYZ(;kk;;kkb)

----
----

== Functions ==
The current Sun Report Builder (verson 1.0.x) includes functions in the following categories:

'''Datetime''' 
DATE, DATEDIF, DATEVALUE, DAY, DAYS, HOUR, MINUTE, MONTH, NOW, SECOND, TIME, TIMEVALUE, TODAY, WEEKDAY, YEAR

'''Financial''' 
Financial

'''Information''' 
CHOOSE, COUNT, COUNTA, COUNTBLANK, HASCHANGED, ISBLANK, ISERR, ISERROR, ISEVEN, ISLOGICAL, ISNA, ISNONTEXT, ISNUMBER, ISODD, ISREF, ISTEXT, NA

'''Logical''' 
AND, FALSE, IF, NOT, OR, TRUE, XOR

'''Math''' 
ABS, AVERAGE, EVEN, MAX, MAXA, MIN, MINA, MOD, ODD, SUM

'''Rounding''' 
INT

'''Text''' 
EXACT, FIND, LEFT, LEN, LOWER, MID, REPLACE, REPT, RIGHT, SUBSTITUTE, T, TEXT, TRIM, UNICHAR, UNICODE, UPPER, URLENCODE

'''Userdefined''' 
NULL

A detailed explanation of the above functions will be found [[Base/Reports/Functions|here.]]
Additional details and code can be found [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Functions here].

CONCAT or CONCATENATE functions not supported, but you can use [Textfieldname]&" "&[Textfieldname] to concatenate text fields, not forget to format it as text.

Please note that these functions are specific to the SRB. Additional functionality may be obtained from the database backend capabilities. For example, if you are using OpenOffice.org's native HSQL database, then you may also use HSQL functions and stored procedures along with OpenOffice.org's queries to generate a wide variety of information shown in reports.

----
----

== Examples ==
=== Function Example ===
The illustration below shows how subtotal fields are created in Report Builder, using functions:

[[Image:SumFieldInReportBuilder.jpg]]

The report source table is shown on the upper left.

The resulting report layout is illustrated below the table. A group has been defined on the plProductType field. The sum field is created on the group footer. The rightmost part of the image shows the definition of a function that serves as the data source for the sum field.

=== Query Example ===
The URL below shows how to use queries in Report Builder:

See [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Example here].

=== Computed Fields Example ===
Computed fields can be created in the way that the formula is entered directly into the data field.

E.g. 100*[Population]/[PopulationCount] to get the percentage of the current population
= Charts in report builder =
You can insert Chart into report builder report, into any places, but only some has a good reason to do.

Not wise to add to details section, it is for single data output, the headers and footer the right place for charts where you print summarized data, and chart for explaining data series, trends, etc.

Open report for edit, and insert Chart into Group/Page/Report header/footer.

When you inserted it shows columns chart as default, now needs to bound to some data source, Select Table/Query/SQL commands. When you selected, the chart shows data what can retrieve from data source.

When you decide to use chart in report useful to create query, which contain only that data what you want to show in that place, without excessive data, because you can not remove them with data ranges dialog as you can do in Calc.

The Charts in report builder has bunch of limitations:

The “First row as label” grayed out and as default selected the data source field names (or aliases names), this is not changeable in through UI in report builder. For this reason I suggest to use query or SQL commands as report/chart source not a Table.

[[Image:]]

The first field data (column in Calc and in Chart) in table or query, can be used as categories, by selecting “First column as label ”.

The field names bounded to the places in table, the counting starts from 0, the first field is 0.

The first field name presented as “label 0”, the second field name is“label1”, … etc.

[[Image:]]

You can not select data series interactively, only can remove whole data series from chart. The data series range not changeable, it contain whole data in table/query, and it has an ugly name “0”, “1”, … etc., which you can see in data series window.

[[Image:]]

The Categories not changeable, it is hard coded to data fields.

== Extensions ==
=== EuroOffice Map Chart ===
One extension further extends the functionality of Sun Report Builder. A detailed description of its use together with the basic steps of creating your first report can be found [http://www.multiracio.com/eurooffice/support/tutorials/eurooffice-map-chart-tutorials/how-to-use-map-charts-with-sun-report-builder here]. This tutorial goes from creating your first report to defining a quite complicated new function, so it can be a useful resource for beginners and advanced users alike (not just for those looking for a way to create map charts).

[[Category:Sun Report Builder]]
[[Category: Base Documentation]]

[[ru:RU/SUN Report Builder/Documentation]]

Base újdonságai a 3.4-s változatban

2011-04-17T12:24:40Z

R4zoli:

= OOo Base 3.4 újdonságai =
Ez a változat az előzőhöz hasonlóan leginkább hibajavításokat tartalmaz, a néhány új jellemzőtől eltekintve. A beépített HSQLDB frissítése a 2.x változatra újra elhalasztásra került, de az már világos, hogy a következő változat tartalmazni fogja.

Az új tulajdonságok:

== Base főablak ==
== Objektum fák: az elemek a nevük alapján kiválaszthatók ==
A Base főablak listái, mostantól támogatja a nevek szerinti kiválasztást, a begépelés során.

Ez a „kiválasztás ahogy gépelsz” tulajdonság, hasonlóan működik mint a legördülő menükhöz, (a legördülő menüktől került ide ez a tulajdonság), vagyis:

* valamely betű beütésével, kiválasztásra kerül az az elem, amely ezzel a betűvel kezdődik
* ha a betűt többször ismételten beütjük, az ezzel a betűvel kezdődő elemek sorban ciklikusan kiválasztásra kerülnek, feltételezve azt, hogy több elem kezdődik azonos betűvel

* a begépelt karaterekből összeállított belső kereső string, rövid inaktivitás után alaphelyzetbe áll

* az elemek más uton történő kiválasztása (Pl. egér vagy nyílbillentyűk) is alaphelyzetbe állítja a belső kereső stringet

=== Mozilla-címjegyzék támogatása lecsrélve a SeaMonkey-címjegyzékre ===
Mivel a Mozilla elég régen lecserélére került a SeaMonkey-el, és a felhasználói profiluk is inkompatibilis módon változott, ezért az OOo-ban is lecserélésre került a Mozzilla-címjegyzék a SeaMonkey-címjegyzékre.

Ez azt jelenti, hogy az összes olyan helyen, ahol a Mozzilla-címjegyzék szerepelt a felhasználói felületen (pl. az „Új adatbázis” tündérnél) a SeaMonkey-címjegyzék szerepel mostantól.

Úgyan így, a meglévő .odb dokumentumok, amelyek eddig a Mozilla-címjegyzéket érték el, mostantól megpróbálják a SeaMonkey-címjegyzéket elérni.

[[Image:Seamonkey.png]]

== Űrlapok ==
=== Listapanel: „Kapcsolt mező” beállításainál is engedélyezett a 0 ===
A Lista panel „Kapcsolt mező” tulajdonságánál, amely meghatározza azt, hogy tábla melyik mezőjét használja az adatcseréhez a listapanel, mostantól beállítható a „0” (nulla) értéke.

Mivel az az érték mindig a figyelembe vette a nullát, az eddigi minimum érték az „1” a tábla második mezőjére hivatkozott, azt követelte meg, hogy a kapcsolódó tábla legalább két mezőt kellet, hogy tartalmazzon.

Nem volt valós oka annak, hogy ez nem lehet „0” (kivéve néhány nagyon régi probléma, amely időközben megoldásra került ), ezért ez a korlátozás eltávolításra került.

[[Image:Listapanel_kapcs_mezo.PNG]]

=== A szöveges adatbázisok adattípusainak megállapításához szükséges sorok száma ===
A MaxRowScan beállítása lehetővé teszi azt, hogy meghatározzuk menníi sort vizsgáljunk át a mező típusának korrek megállapítására. Korábban egy sor adatai alapján történt ez a meghatározás.

A Szerkesztés>Adatbázis>Speciális beállítások alatt változtatható ez az érték, csak a szöveges állományokhoz csatlakozó .odb fájlok esetében.

[[Image:Rowscan1.png]]

File:Listapanel kapcs mezo.PNG

2011-04-17T12:24:01Z

R4zoli: uploaded a new version of "File:Listapanel kapcs mezo.PNG": Reverted to version as of 12:22, 17 April 2011

File:Listapanel kapcs mezo.PNG

2011-04-17T12:23:08Z

R4zoli: uploaded a new version of "File:Listapanel kapcs mezo.PNG": Reverted to version as of 12:21, 17 April 2011

File:Listapanel kapcs mezo.PNG

2011-04-17T12:22:35Z

R4zoli: uploaded a new version of "File:Listapanel kapcs mezo.PNG"

File:Listapanel kapcs mezo.PNG

2011-04-17T12:21:05Z

R4zoli: uploaded a new version of "File:Listapanel kapcs mezo.PNG"

File:Listapanel kapcs mezo.PNG

2011-04-17T12:19:10Z

R4zoli:

Base újdonságai a 3.4-s változatban

2011-04-17T12:17:17Z

R4zoli: Created page with '= OOo Base 3.4 újdonságai = Ez a változat az előzőhöz hasonlóan leginkább hibajavításokat tartalmaz, a néhány új jellemzőtől eltekintve. A beépített HSQLDB friss…' (checkpoint save)

= OOo Base 3.4 újdonságai =
Ez a változat az előzőhöz hasonlóan leginkább hibajavításokat tartalmaz, a néhány új jellemzőtől eltekintve. A beépített HSQLDB frissítése a 2.x változatra újra elhalasztásra került, de az már világos, hogy a következő változat tartalmazni fogja.

Az új tulajdonságok:

== Base főablak ==
== Objektum fák: az elemek a nevük alapján kiválaszthatók ==
A Base főablak listái, mostantól támogatja a nevek szerinti kiválasztást, a begépelés során.

Ez a „kiválasztás ahogy gépelsz” tulajdonság, hasonlóan működik mint a legördülő menükhöz, (a legördülő menüktől került ide ez a tulajdonság), vagyis:

* valamely betű beütésével, kiválasztásra kerül az az elem, amely ezzel a betűvel kezdődik
* ha a betűt többször ismételten beütjük, az ezzel a betűvel kezdődő elemek sorban ciklikusan kiválasztásra kerülnek, feltételezve azt, hogy több elem kezdődik azonos betűvel

* a begépelt karaterekből összeállított belső kereső string, rövid inaktivitás után alaphelyzetbe áll

* az elemek más uton történő kiválasztása (Pl. egér vagy nyílbillentyűk) is alaphelyzetbe állítja a belső kereső stringet

=== Mozilla-címjegyzék támogatása lecsrélve a SeaMonkey-címjegyzékre ===
Mivel a Mozilla elég régen lecserélére került a SeaMonkey-el, és a felhasználói profiluk is inkompatibilis módon változott, ezért az OOo-ban is lecserélésre került a Mozzilla-címjegyzék a SeaMonkey-címjegyzékre.

Ez azt jelenti, hogy az összes olyan helyen, ahol a Mozzilla-címjegyzék szerepelt a felhasználói felületen (pl. az „Új adatbázis” tündérnél) a SeaMonkey-címjegyzék szerepel mostantól.

Úgyan így, a meglévő .odb dokumentumok, amelyek eddig a Mozilla-címjegyzéket érték el, mostantól megpróbálják a SeaMonkey-címjegyzéket elérni.

[[Image:]]

== Űrlapok ==
=== Listapanel: „Kapcsolt mező” beállításainál is engedélyezett a 0 ===
A Lista panel „Kapcsolt mező” tulajdonságánál, amely meghatározza azt, hogy tábla melyik mezőjét használja az adatcseréhez a listapanel, mostantól beállítható a „0” (nulla) értéke.

Mivel az az érték mindig a figyelembe vette a nullát, az eddigi minimum érték az „1” a tábla második mezőjére hivatkozott, azt követelte meg, hogy a kapcsolódó tábla legalább két mezőt kellet, hogy tartalmazzon.

Nem volt valós oka annak, hogy ez nem lehet „0” (kivéve néhány nagyon régi probléma, amely időközben megoldásra került ), ezért ez a korlátozás eltávolításra került.

[[Image:]]

=== A szöveges adatbázisok adattípusainak megállapításához szükséges sorok száma ===
A MaxRowScan beállítása lehetővé teszi azt, hogy meghatározzuk menníi sort vizsgáljunk át a mező típusának korrek megállapítására. Korábban egy sor adatai alapján történt ez a meghatározás.

A Szerkesztés>Adatbázis>Speciális beállítások alatt változtatható ez az érték, csak a szöveges állományokhoz csatlakozó .odb fájlok esetében.

[[Image:]]

Kezdőlap

2011-04-17T12:16:34Z

R4zoli: /* Az OpenOffice.org 3.3 újdonságai */

== Üdvözli az OpenOffice.org wiki ==
A wiki az OpenOffice.org (OOo) felhasználóinak / fejlesztőinek készült. A felhasználók egyre növekvő száma is szükségessé tesz a [http://hu.openoffice.org magyar OOo honlapon] kívüli információforrást.
Az itt található linkekre kattintva közvetlenül eljuthat a kiválasztott oldalra.

Csatlakozzon az OpenOffice.org wiki készítőihez. Lehetőleg használja az OOo bejelentkezési nevét a regisztrációjakor. (A későbbiekben összevonásra kerülhet a két rész.) Néhány funkciót csak a bejelentkezett felhasználók használhatnak, a spamelés elkerülésére. A regisztráció része a levelezési cím ellenőrzése.

== Fórumok ==
Az alábbi fórumokon választ kaphat a feltett kérdésére, kereshet a korábbi témák között.

Magyar nyelven:
[http://user.services.openoffice.org/hu/forum/ OpenOffice.org Közösségi Fórum]

Valamint a:
[http://hup.hu/forum/192 HUP iroda fórum]

Angolul:
[http://user.services.openoffice.org/en/forum/ OpenOffice.org Community Forum]

----
== Az OpenOffice.org 3.4 újdonságai ==
[[Base újdonságai a 3.4-s változatban]]

== Az OpenOffice.org 3.3 újdonságai ==
[[Base újdonságai a 3.3-s változatban]]

== Az OpenOffice.org 3.2 újdonságai ==
[[Base újdonságai a 3.2-s változatban]]

== Az OpenOffice.org 3.1 újdonságai ==
[http://www.openoffice.hu/2009/05/az-openoffice-31-ujdonsagai/ Az OpenOffice.org 3.1 újdonságai]

[[Base újdonságai a 3.1-s változatban]]

== Az OpenOffice.org 3.0 újdonságai ==
[http://hu.openoffice.org/files/documents/176/4324/OpenOffice.org3_ujdonsagai.pdf 3.0 újdonságai]

== Az OpenOffice.org 2.4 újdonságai ==
[[2.4 változat újdonságai]]

== Dokumentáció ==

Az OpenOffice.org használatával kapcsolatos dokumentációk ebben a wikiben:

[[HU/Documentation/BASIC_Guide|OpenOffice.org BASIC programozói útmutató]]

== Fejlesztés ==
Az OpenOffice.org magyar fejlesztésével kapcsolatos oldalak.

[[Hu.openoffice.org/Magyar_Ispell_hibabejelent%C3%A9s|Magyar Ispell hibabejelentés]]

[[Hu.openoffice.org/Szabad_diploma_-_OOo|Szabad diploma - OOo]]

[[Hu.openoffice.org/Minőségbiztosítás|Minőségbiztosítás - VCLTesttool]]

{{InterWiki Languages}}

[[Category:Magyar]]

Base/New features in 3 4

2011-04-17T10:52:09Z

R4zoli: /* OOo Base 3.4 new features */

= OOo Base 3.4 new features =
This version contains mostly bugfixes, only small number of new features introduced in this version.

The HSQLDB 2.x built-in database engine integration, postponed again, now clear that the next version will contain the actual version of HSQLDB.

The new features listed below:

== Main Base window ==
=== Object trees: selecting entries by typing their name ===
The tree lists in Base's main application window, now support selecting entries by typing their name.

This "select as you type" feature, works pretty much like the same feature in normal list boxes
(in fact, the implementation for the latter has simply been outsourced, abstracted, and applied to tree lists), i.e.:

* typing some letters will select the entry which starts with those letters
* typing the same letter repeatedly will cycle through the entries which start with this letter, assuming there is no single entry which starts with multiple occurrences of it

* the internal search string, assembled by the characters you type, is reset after a small amount of time of inactivity

* selecting entries by other means than the quick search (e.g. the keyboard or the mouse) also resets the internal search string 

=== Mozilla Address Book support removed, in favour of Seamonkey ===
Since the Mozilla product has long been superseded by the SeaMonkey suite, and the profile formats of both changed incompatibly, the Mozilla Address Book support in OpenOffice.org has been removed, in favor of support for the SeaMonkey address books.

This means that all places in the UI which referred to a Mozilla Address Book (e.g. in the "New Database" wizard) have been adjusted to refer to SeaMonkey instead.

Also, existing .odb documents accessing Mozilla Address Books will now attempt to access SeaMonkey Address Books.

[[Image:Seamonkey.png‎]]

== Forms ==
=== List box controls: "Bound field" is allowed to be 0, too ===
The "Bound field" property of a list box control, specifying which column of the list boxes result set should be used for data exchange, can have the value "0" now.

Given that the value was always 0-based (i.e. "1" refers to the second column in the result set), the former minimum value "1" implied that the list result set must have at least two columns for the list box to be of use.

There was no real reason for this limitation to not allow "0" (except some stone-aged implementation quirks, which have been exorcised), so it has been removed.

[[Image:Bound_field.png]]

=== Scan rows for correct type information for Text databases ===
The MaxRowScan setting allows to define how many rows should be scanned to find the correct type of a column. In the past only the first row was scanned.

You can set it in Edit>Database>Advanced settings Special settings tab, for text source connected databases.

[[Image:Rowscan1.png]]

Base/New features in 3 4

2011-04-17T10:49:53Z

R4zoli: /* Scan rows for correct type information for Text databases */

= OOo Base 3.4 new features =
This version contains mostly bugfixes, only small number of new features introduced in this version.

The HSQLDB 2.x built-in database engine integration, postponed again, now clear that the next version will contain the actual version.

The new features:

== Main Base window ==
=== Object trees: selecting entries by typing their name ===
The tree lists in Base's main application window, now support selecting entries by typing their name.

This "select as you type" feature, works pretty much like the same feature in normal list boxes
(in fact, the implementation for the latter has simply been outsourced, abstracted, and applied to tree lists), i.e.:

* typing some letters will select the entry which starts with those letters
* typing the same letter repeatedly will cycle through the entries which start with this letter, assuming there is no single entry which starts with multiple occurrences of it

* the internal search string, assembled by the characters you type, is reset after a small amount of time of inactivity

* selecting entries by other means than the quick search (e.g. the keyboard or the mouse) also resets the internal search string 

=== Mozilla Address Book support removed, in favour of Seamonkey ===
Since the Mozilla product has long been superseded by the SeaMonkey suite, and the profile formats of both changed incompatibly, the Mozilla Address Book support in OpenOffice.org has been removed, in favor of support for the SeaMonkey address books.

This means that all places in the UI which referred to a Mozilla Address Book (e.g. in the "New Database" wizard) have been adjusted to refer to SeaMonkey instead.

Also, existing .odb documents accessing Mozilla Address Books will now attempt to access SeaMonkey Address Books.

[[Image:Seamonkey.png‎]]

== Forms ==
=== List box controls: "Bound field" is allowed to be 0, too ===
The "Bound field" property of a list box control, specifying which column of the list boxes result set should be used for data exchange, can have the value "0" now.

Given that the value was always 0-based (i.e. "1" refers to the second column in the result set), the former minimum value "1" implied that the list result set must have at least two columns for the list box to be of use.

There was no real reason for this limitation to not allow "0" (except some stone-aged implementation quirks, which have been exorcised), so it has been removed.

[[Image:Bound_field.png]]

=== Scan rows for correct type information for Text databases ===
The MaxRowScan setting allows to define how many rows should be scanned to find the correct type of a column. In the past only the first row was scanned.

You can set it in Edit>Database>Advanced settings Special settings tab, for text source connected databases.

[[Image:Rowscan1.png]]

File:Rowscan1.png

2011-04-17T10:49:29Z

R4zoli:

Base/New features in 3 4

2011-04-17T10:48:52Z

R4zoli: /* List box controls: "Bound field" is allowed to be 0, too */

= OOo Base 3.4 new features =
This version contains mostly bugfixes, only small number of new features introduced in this version.

The HSQLDB 2.x built-in database engine integration, postponed again, now clear that the next version will contain the actual version.

The new features:

== Main Base window ==
=== Object trees: selecting entries by typing their name ===
The tree lists in Base's main application window, now support selecting entries by typing their name.

This "select as you type" feature, works pretty much like the same feature in normal list boxes
(in fact, the implementation for the latter has simply been outsourced, abstracted, and applied to tree lists), i.e.:

* typing some letters will select the entry which starts with those letters
* typing the same letter repeatedly will cycle through the entries which start with this letter, assuming there is no single entry which starts with multiple occurrences of it

* the internal search string, assembled by the characters you type, is reset after a small amount of time of inactivity

* selecting entries by other means than the quick search (e.g. the keyboard or the mouse) also resets the internal search string 

=== Mozilla Address Book support removed, in favour of Seamonkey ===
Since the Mozilla product has long been superseded by the SeaMonkey suite, and the profile formats of both changed incompatibly, the Mozilla Address Book support in OpenOffice.org has been removed, in favor of support for the SeaMonkey address books.

This means that all places in the UI which referred to a Mozilla Address Book (e.g. in the "New Database" wizard) have been adjusted to refer to SeaMonkey instead.

Also, existing .odb documents accessing Mozilla Address Books will now attempt to access SeaMonkey Address Books.

[[Image:Seamonkey.png‎]]

== Forms ==
=== List box controls: "Bound field" is allowed to be 0, too ===
The "Bound field" property of a list box control, specifying which column of the list boxes result set should be used for data exchange, can have the value "0" now.

Given that the value was always 0-based (i.e. "1" refers to the second column in the result set), the former minimum value "1" implied that the list result set must have at least two columns for the list box to be of use.

There was no real reason for this limitation to not allow "0" (except some stone-aged implementation quirks, which have been exorcised), so it has been removed.

[[Image:Bound_field.png]]

=== Scan rows for correct type information for Text databases ===
The MaxRowScan setting allows to define how many rows should be scanned to find the correct type of a column. In the past only the first row was scanned.

You can set it in Edit>Database>Advanced settings Special settings tab, for text source connected databases.

[[Image:]]

File:Bound field.png

2011-04-17T10:48:30Z

R4zoli:

Base/New features in 3 4

2011-04-17T10:47:55Z

R4zoli: /* Mozilla Address Book support removed, in favour of Seamonkey */

= OOo Base 3.4 new features =
This version contains mostly bugfixes, only small number of new features introduced in this version.

The HSQLDB 2.x built-in database engine integration, postponed again, now clear that the next version will contain the actual version.

The new features:

== Main Base window ==
=== Object trees: selecting entries by typing their name ===
The tree lists in Base's main application window, now support selecting entries by typing their name.

This "select as you type" feature, works pretty much like the same feature in normal list boxes
(in fact, the implementation for the latter has simply been outsourced, abstracted, and applied to tree lists), i.e.:

* typing some letters will select the entry which starts with those letters
* typing the same letter repeatedly will cycle through the entries which start with this letter, assuming there is no single entry which starts with multiple occurrences of it

* the internal search string, assembled by the characters you type, is reset after a small amount of time of inactivity

* selecting entries by other means than the quick search (e.g. the keyboard or the mouse) also resets the internal search string 

=== Mozilla Address Book support removed, in favour of Seamonkey ===
Since the Mozilla product has long been superseded by the SeaMonkey suite, and the profile formats of both changed incompatibly, the Mozilla Address Book support in OpenOffice.org has been removed, in favor of support for the SeaMonkey address books.

This means that all places in the UI which referred to a Mozilla Address Book (e.g. in the "New Database" wizard) have been adjusted to refer to SeaMonkey instead.

Also, existing .odb documents accessing Mozilla Address Books will now attempt to access SeaMonkey Address Books.

[[Image:Seamonkey.png‎]]

== Forms ==
=== List box controls: "Bound field" is allowed to be 0, too ===
The "Bound field" property of a list box control, specifying which column of the list boxes result set should be used for data exchange, can have the value "0" now.

Given that the value was always 0-based (i.e. "1" refers to the second column in the result set), the former minimum value "1" implied that the list result set must have at least two columns for the list box to be of use.

There was no real reason for this limitation to not allow "0" (except some stone-aged implementation quirks, which have been exorcised), so it has been removed.

[[Image:]]

=== Scan rows for correct type information for Text databases ===
The MaxRowScan setting allows to define how many rows should be scanned to find the correct type of a column. In the past only the first row was scanned.

You can set it in Edit>Database>Advanced settings Special settings tab, for text source connected databases.

[[Image:]]

File:Seamonkey.png

2011-04-17T10:47:14Z

R4zoli:

Base/New features in 3 4

2011-04-15T13:44:17Z

R4zoli: Created page with '= OOo Base 3.4 new features = This version contains mostly bugfixes, only small number of new features introduced in this version. The HSQLDB 2.x built-in database engine integr…' (checkpoint save)

= OOo Base 3.4 new features =
This version contains mostly bugfixes, only small number of new features introduced in this version.

The HSQLDB 2.x built-in database engine integration, postponed again, now clear that the next version will contain the actual version.

The new features:

== Main Base window ==
=== Object trees: selecting entries by typing their name ===
The tree lists in Base's main application window, now support selecting entries by typing their name.

This "select as you type" feature, works pretty much like the same feature in normal list boxes
(in fact, the implementation for the latter has simply been outsourced, abstracted, and applied to tree lists), i.e.:

* typing some letters will select the entry which starts with those letters
* typing the same letter repeatedly will cycle through the entries which start with this letter, assuming there is no single entry which starts with multiple occurrences of it

* the internal search string, assembled by the characters you type, is reset after a small amount of time of inactivity

* selecting entries by other means than the quick search (e.g. the keyboard or the mouse) also resets the internal search string 

=== Mozilla Address Book support removed, in favour of Seamonkey ===
Since the Mozilla product has long been superseded by the SeaMonkey suite, and the profile formats of both changed incompatibly, the Mozilla Address Book support in OpenOffice.org has been removed, in favor of support for the SeaMonkey address books.

This means that all places in the UI which referred to a Mozilla Address Book (e.g. in the "New Database" wizard) have been adjusted to refer to SeaMonkey instead.

Also, existing .odb documents accessing Mozilla Address Books will now attempt to access SeaMonkey Address Books.

[[Image:]]

== Forms ==
=== List box controls: "Bound field" is allowed to be 0, too ===
The "Bound field" property of a list box control, specifying which column of the list boxes result set should be used for data exchange, can have the value "0" now.

Given that the value was always 0-based (i.e. "1" refers to the second column in the result set), the former minimum value "1" implied that the list result set must have at least two columns for the list box to be of use.

There was no real reason for this limitation to not allow "0" (except some stone-aged implementation quirks, which have been exorcised), so it has been removed.

[[Image:]]

=== Scan rows for correct type information for Text databases ===
The MaxRowScan setting allows to define how many rows should be scanned to find the correct type of a column. In the past only the first row was scanned.

You can set it in Edit>Database>Advanced settings Special settings tab, for text source connected databases.

[[Image:]]

Database

2011-04-15T13:35:10Z

R4zoli: /* General */

{{Template:Base Project}}
{{Database/Lang|Database}}

This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add missing documents to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting Started with Base)
: [http://wiki.services.openoffice.org/w/images/3/3c/0108GS33-GettingStartedWithBase.pdf Getting Started with Base] - ''PDF''
: or Getting Started with Base [[Documentation/OOo3_User_Guides/Getting_Started/Getting_Started_with_Base|wiki version]]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* Base Guide
:[[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning|Base Guide Planning]]
:Base Guide Outline Proposal from OOoAuthors

* Mid Level Base Tutorial
: [http://openoffice.org/projects/documentation/downloads/directory/Base/Mid%20level%20Base%20tutorial Mid Level Base Tutorial]
: Initial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"- From getting started to more advanced
: [http://sheepdogguides.com/fdb/fdb1main.htm Tutorials and "How to"s... 45 from one author at Sheepdogguides.com]
: Initial author: TK Boyd
: Both specific tasks and fundamental skills are explained.
: A section introducing the use of macros added 5/09.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.2
: [[Base/New_features_in_3_2|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.3
: [[Base/New_features_in_3_3|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.4
: [[Base/New_features_in_3_4|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description followed''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
*FAQ (Base)
: [[FAQ_(Base)|FAQ_(Base)]]

* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

* Using csv/text files as editable data source.
: [http://user.services.openoffice.org/en/forum/viewtopic.php?f=83&t=23260 OOo users forum Tutorial]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

* Three table example, with supporting essay- Project management
: [http://sheepdogguides.com/fdb/fdb7peopproj.htm Link to essay, which has link to download a small database]
: The database illustrates techniques explained in the essay. It is provided as an illustration, not for the data it contains.

* Base Example
: [[File:DerbyToursDB.odb]]
: [[User:HCPotter]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the corresponding links.

*[[FR/Documentation/HSQLDB Guide]]
*[[FR/Documentation/Base/Nouvelles Fonctions 3 1]]

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

* [[OpenOffice_per_JDBC_an_Informix | Anbindung von OpenOffice an Informix per JDBC]]

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Español=
El siguiente Links esta escrito en español.

http://wiki.services.openoffice.org/wiki/ES/Database

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Project]]
[[fa:FA/Localization:Database]]

Database

2011-03-04T06:19:08Z

R4zoli: /* General */

{{Template:Base Project}}
{{Database/Lang|Database}}

This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add missing documents to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting Started with Base)
: [http://wiki.services.openoffice.org/w/images/3/3c/0108GS33-GettingStartedWithBase.pdf Getting Started with Base] - ''PDF''
: or Getting Started with Base [http://wiki.services.openoffice.org/wiki/Documentation/OOo3_User_Guides/Getting_Started/Getting_Started_with_Base wiki version]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* Base Guide
:[http://wiki.services.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Base_Guide/Planning Base Guide Planning]
:Base Guide Outline Proposal from OOoAuthors

* Mid Level Base Tutorial
: [http://documentation.openoffice.org/servlets/ProjectDocumentList?folderID=778&expandFolder=778&folderID=597 Mid Level Base Tutorial]
: Innitial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"- From getting started to more advanced
: [http://sheepdogguides.com/fdb/fdb1main.htm Tutorials and "How to"s... 45 from one author at Sheepdogguides.com]
: Initial author: TK Boyd
: Both specific tasks and fundamental skills are explained.
: A section introducing the use of macros added 5/09.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.2
: [[Base/New_features_in_3_2|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.3
: [[Base/New_features_in_3_3|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description followed''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
*FAQ (Base)
: [[FAQ_(Base)|FAQ_(Base)]]

* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

* Using csv/text files as editable data source.
: [http://user.services.openoffice.org/en/forum/viewtopic.php?f=83&t=23260 OOo users forum Tutorial]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

* Three table example, with supporting essay- Project management
: [http://sheepdogguides.com/fdb/fdb7peopproj.htm Link to essay, which has link to download a small database]
: The database illustrates techniques explained in the essay. It is provided as an illustration, not for the data it contains.

* Base Example
: [[File:DerbyToursDB.odb]]
: [[User:HCPotter]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the corresponding links.

*[[FR/Documentation/HSQLDB Guide]]
*[[FR/Documentation/Base/Nouvelles Fonctions 3 1]]

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

* [[OpenOffice_per_JDBC_an_Informix | Anbindung von OpenOffice an Informix per JDBC]]

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Español=
El siguiente Links esta escrito en español.

http://wiki.services.openoffice.org/wiki/ES/Database

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Project]]

Database/Drivers/MySQL Native/1.0

2011-01-10T11:55:58Z

R4zoli: /* Status */

{{DISPLAYTITLE:MySQL Connector for OpenOffice.org 1.0}}

== Introduction ==

MySQL Connector for OpenOffice.org is a [http://www.mysql.org MySQL] driver for [http://www.openoffice.org/ OpenOffice.org]. It can be used to connect from [http://download.openoffice.org OpenOffice.org 3.1] to a MySQL server 5.1 or newer.

Before MySQL Connector for OpenOffice.org became available you'd have to use [http://dev.mysql.com/downloads/connector/j/ MySQL Connector/J (JDBC)] or [http://dev.mysql.com/downloads/connector/odbc/ MySQL Connector for ODBC] to connect to a MySQL server.

Therefore the driver is also referred to as a native driver in the context of OpenOffice.org. The term native driver clashes with the MySQL definition of a native driver: MySQL Connector for OpenOffice.org does not implement the MySQL Client Server protocol. Technically speaking the MySQL Connector for OpenOffice.org is implemented as a proxy on top of the [http://dev.mysql.com/doc/refman/5.1/en/connector-cpp.html MySQL Connector/C++].

The driver is delivered as an OpenOffice.org extension.

=== Advantages ===

Using MySQL Connector for OpenOffice.org has the following advantages:

*Easy installation through the OpenOffice.org Extension Manager.
*Seamless integration into OpenOffice.org.
*Work on multiple MySQL schemata (databases) simultaneously
*Connect to MySQL servers using named pipes (Windows) or Sockets (Unix)
*No need to go through an additional Connector installation routine (ODBC/JDBC)
*No need to configure or register an additional Connector (ODBC)
*No need to install or configure a driver manager (ODBC)
*No need for a Java Runtime Environment (JDBC)

=== Status ===

The MySQL Connector for OpenOffice.org is released in version 1.0.1, in production quality.

== Installation ==

=== Install or upgrade to OpenOffice.org 3.1 ===

OpenOffice.org 3.1 is available from OpenOffice.org's [http://download.openoffice.org download site]. The driver does not work together with earlier versions of OpenOffice.org. It will also run in OpenOffice.org when it becomes available, but not in current developer snapshots (up to, anticipated, DEV300.m57).

Please use "vanilla" OpenOffice.org: As with all extensions containing binary code, they're potentially incompatible with other OpenOffice.org distributions (like the one from your favorite Linux distribution), and are not necessarily expected to work with them. If you're using an OpenOffice.org build obtained elsewhere, e.g. by your favorite Linux distributor, then please ask this source to also provide the MySQL Connector for OpenOffice.org.

=== Download MySQL Connector for OpenOffice.org ===

The extension is available from the [http://extensions.services.openoffice.org/project/mysql_connector OpenOffice.org extensions repository]. It is provided for the usual 6 platforms (Windows, Linux Intel 32 Bit, Linux Intel 64 Bit, Solaris Sparc, Solaris Intel 32 Bit, Mac OS X Intel).

Download the file to a location of your choice, for example <code>My Documents</code> or <code>~/Documents</code>.

=== Users of the Beta version please note ===

If you have installed the previous Beta version please uninstall it first manually in the Extension Manager. The final version has a new product name and therefore it is not possible to update it via the extension mechanism. Also delete the cached database connection that was previously created as it cannot be re-used again (e.g., Windows: <code>"C:\Documents and Settings\<user>\Application Data\OpenOffice.org\3\user\uno_packages\cache\registry\*"</code> or Unix: <code>"/home/<user>/.openoffice.org/3/user/uno_packages/cache/registry/*"</code>).

=== Installing the extension ===

Add the <code>.oxt</code> extension through the Extension Manager of OpenOffice.org. In OpenOffice.org, select <code>Tools, Extension Manager...</code> and specify the <code>.oxt</code> file as a new extension. When done, MySQL Connector for OpenOffice.org should show up as a new extension under <code>My Extensions</code>.

[[Image:Conn ooo 1.0 GA extensions.png]]

Restart OpenOffice.org to complete the installation.

== Getting Started: Connecting to MySQL ==

MySQL Connector for OpenOffice.org allows you to access the MySQL Server and its schemata from the OpenOffice.org suite.

The following example demonstrates the creation of a new OpenOffice.org Base database which uses a local MySQL Server for storage and the new connector for connecting.

=== Select the database ===

Create a new database (<code>File, New, Database</code>). This starts a wizard that allows you to create a new, open an existing, or connect to existing database. Select the latter option.

From the drop-down list, select <code>MySQL</code>. Click <code>Next >></code>.

[[Image:Conn ooo alpha wizard1.png]]

=== Select the type of the driver ===

You can use three different MySQL drivers for connecting to MySQL from OpenOffice.org. You can choose a generic ODBC or JDBC connection method or the native driver. Select <code>Connect native</code>. Click <code>Next >></code>.

[[Image:Conn ooo alpha wizard2.png]]

=== Setting up the database connection ===

Set up the database connection. Put the schema (database) you want to connect to into <code>Name of the database</code>. Enter the URL (host name, or simply type <code>localhost</code> when connecting to the server on your own PC), Port and Socket (or leave socket empty) of your MySQL Server. Click <code>Next >></code>.

[[Image:Conn ooo alpha wizard3.png]]

=== Fill in user credentials ===

Provide the user credentials for connecting to your MySQL Server. Click <code>Next >></code>.

[[Image:Conn ooo alpha wizard4.png]]

=== Save and proceed ===

Finish the wizard. All defaults are a safe choice. Click <code>Finish >></code>.

[[Image:Conn ooo alpha wizard5.png]]

== Getting Started: Usage Examples ==

=== Listing Tables ===

In the Database area of the Base main window, select Tables. If this is the first time you're accessing the database you'll be prompted for your credentials (username and password); you can store these settings for your current Base session.

[[Image:Conn ooo alpha base.png]]

Depending on your connection settings you will now see all databases with all their tables, or just the database you've specified in the connection settings.

== Known Issues ==

There is currently [[Database/Drivers/MySQL Native/1.0/Known Issues|1 known issue]] in MySQL Connector for OpenOffice.org. We decided to nonetheless release version 1.0, since we think that it's better for all users, which do not encounter this particular problem, to benefit from this great extension.

== Contact ==

If you discover a bug, or just want to give any kind of feedback on the connector, please send an email to [mailto:users@dba.openoffice.org users@dba.openoffice.org]. It's a low-volume list with less than 10 mails per day. If you prefer reading it by means other than subscribing to it, see [[Base Mailing List|here]].

[[Category:Database_Drivers]] [[fr:FR/Documentation/Base/MySQL Connector|fr:FR/Documentation/Base/MySQL Connector]]

Database

2010-11-15T12:01:09Z

R4zoli: /* General */ (checkpoint save)

{{Database/Lang|Database}}
This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add missing documents to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting Started with Base)
: [http://documentation.openoffice.org/manuals/oooauthors2/0110GS-GettingStartedWithBase.pdf Getting Started with Base] - ''PDF''
: or Getting Started with Base [http://wiki.services.openoffice.org/wiki/Documentation/OOo3_User_Guides/Getting_Started/Getting_Started_with_Base wiki version]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* Base Guide
:[http://wiki.services.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Base_Guide/Planning Base Guide Planning]
:Base Guide Outline Proposal from OOoAuthors

* Mid Level Base Tutorial
: [http://documentation.openoffice.org/servlets/ProjectDocumentList?folderID=778&expandFolder=778&folderID=597 Mid Level Base Tutorial]
: Innitial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"- From getting started to more advanced
: [http://sheepdogguides.com/fdb/fdb1main.htm Tutorials and "How to"s... 45 from one author at Sheepdogguides.com]
: Initial author: TK Boyd
: Both specific tasks and fundamental skills are explained.
: A section introducing the use of macros added 5/09.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.2
: [[Base/New_features_in_3_2|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.3
: [[Base/New_features_in_3_3|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description followed''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
*FAQ (Base)
: [[FAQ_(Base)|FAQ_(Base)]]

* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

* Using csv/text files as editable data source.
: [http://user.services.openoffice.org/en/forum/viewtopic.php?f=83&t=23260 OOo users forum Tutorial]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

* Three table example, with supporting essay- Project management
: [http://sheepdogguides.com/fdb/fdb7peopproj.htm Link to essay, which has link to download a small database]
: The database illustrates techniques explained in the essay. It is provided as an illustration, not for the data it contains.

* Base Example
: [[File:DerbyToursDB.odb]]
: [[User:HCPotter]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the corresponding links.

*[[FR/Documentation/HSQLDB Guide]]
*[[FR/Documentation/Base/Nouvelles Fonctions 3 1]]

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

* [[OpenOffice_per_JDBC_an_Informix | Anbindung von OpenOffice an Informix per JDBC]]

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Castellano=
El siguiente Links esta escrito en castellano.
 
http://wiki.services.openoffice.org/wiki/ES/Database

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Project]]

Base/New features in 3 3

2010-08-19T07:28:03Z

R4zoli: /* Allow to overrule Base's heuristics for primary key support */

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

[[Image:Supports_pk.PNG]]

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:Vert_alignment.png]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:Add_field.png]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:Col_description.PNG]]
[[Category:Database]]

File:Supports pk.PNG

2010-08-19T07:27:18Z

R4zoli:

Base újdonságai a 3.3-s változatban

2010-08-19T07:25:23Z

R4zoli: /* Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére */

== Base általában ==
=== Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége ===
Új opció „Támogatja az elsődleges kulcsokat” az adatbázis kapcsolat „Speciális beállítások” alatt, ezzel lehetővé válik a Base által használt heurisztikus elsődleges kulcs felismerő algoritmusának felülbírálata.

Ez az új opció az ODBC, JDBC, és ADO adatbázis kapcsolatoknál érhető el.

[[Image:Spec_tul.PNG]]

Amikor adatbázishoz olyan általános csatolókon keresztül csatlakozunk, mint az ODBC, JDBC, vagy az ADO.A Base heurisztikus algoritmust használ, annak kiderítésére, hogy az adatbázis támogatja-e az elsődleges kulcsokat, mindezt azért, mert ezen csatolók egyike sem rendelkeznek specifikus támogatással ezen információ lekérdezésér.

Mivel a heurisztikus algoritmus néha hibázik, mostantól új opció „ Támogatja az elsődleges kulcsokat”, található a Szerkesztés>Speciális tulajdonságok>Speciális beállítások alatt. Az opció három állású jelölő négyzet, kijelölt állapot feltételezi az elsődleges kulcs támogatását, a kijelölés nélküli az elsődleges kulcs nem támogatott, a harmadik állapot a „nem meghatározott”, amelyik az alap beállított állapot, „alkalmazd a heurisztikus algoritmust” opciót jelenti.

Ne feledje ez csak azt jelenti, hogy a heurisztikus algoritmus alkalmazásának a felül írása. Ha bejelöli ezt, és az adatbázis nem támogatja az elsődleges kulcsokat, arra számíthat, hogy a Base hibajelzéseket küld vagy megfagy, mivel arra számít, hogy az elsődleges kulcsok támogatottak. Például ha elsődleges kulcsot próbál meg létrehozni a tábla tervezőben,

=== Csak olvasható adatbázis regisztrálásának támogatása ===
Mostantól a Base támogatja a csak olvasható adatbázisok regisztrálását.

Az adatbázis regisztrálására általában az Eszközök>Beállítások>OpenOffice.org Base>Adatbázisok alatt történik. A regisztrációs adatok az OpenOffice.org konfigurációs fájljaiban rögzítettek, ami azt is lehetővé teszi, hogy kiegészítő beállítások részenként is alkalmazhatók (kiterjesztéseken keresztül). Ha ezek a beállítási részek csak olvashatónak kerültek beállításra, a konfigurációs mechanizmuson keresztül, a felhasználói felület e beállításokat figyelembe veszi, nem engedélyezi a regisztrációs bejegyzés módosítását (szerkesztését, eltávolítását).

=== Adatbázis illesztő program kibővítése kiterjesztéssel ===
Részletes információ itt:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

A fenti specifikációból kivonat:

Az SDBC illesztő programok, kibővíthetők [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions kiterjesztésekkel].

A legtöbb illesztő program nem támogatja az olyan speciális tulajdonságokat, mint a nézetek szerkesztése, vagy a kulcsok hozzáadása vagy eldobása. Ezért az alábbi interfészek a kiterjesztés segítségével megvalósíthatók:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration] .

A szükséges tulajdonságok engedélyezésére a kiterjesztésben, az illesztő program konfigurációs bejegyzésének a kibővítésére van szükség. A konfigurációs bejegyzés ellenőrzésére a tulajdonságok bejegyzés alatt kerül sor, ha a szolgáltatás létrehozható a neve kerül felhasználásra. Az alábbiakban található a konfigurációs bejegyzés és a szolgáltatás név egyeztető táblázata:

Konfiguráció neve A megvalósítandó interfész neve

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

Annak engedélyezésére, hogy a fájl formátum specifikációban előírt helytől eltérő helyről is beolvasható legyen a lekérdezés, űrlap vagy jelentés, a kiterjesztés olyan szolgáltatást hozhat létre , amely az alábbi megnevezett interfészeket valósíthatja meg. A megnevezett konfigurációs bejegyzések:

* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier 

amelyek mindegyike az alabbi interfészeket kell, hogy megvalósítsa:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Űrlapok ==
=== Ctrl+F5 gyorsbillentyű ide-oda kapcsol a dokumentum és a legközelebbi vezérlő elem között ===
Ctrl+F5, amit korábban arra használtunk, hogy az első űrlapvezérlő elem kapja meg a fókuszt, ezt a legtöbb felhasználó nehezen értette meg,hogy miért így van, megváltozott.

Mostantól a kurzor pozícióhoz legközelebb álló vezérlőelemre áll ha az nincs a vezérlőelemben. Egyébként visszaadja a fókuszt a dokumentum nézetnek.

=== Az űrlap vezérlőelelmek az őket tartalmazó dokumentum szövegével megegyezően formázódnak ===
Ez az új tulajdonság nem kapcsolódik szorosan a Base-hez, de érdekes lehet.

A vezérlőelemek szövegének formázása megváltozott, igaz ez a változás csak néhány vezérlőelemre és néhány dokumentum típusra korlátozódik.

Az OOo alkalmazások a képernyőn látható szöveget általában az úgynevezett referencia egység beállításai szerint formázzák. Ez lehet a dokumentum részére kiválasztott nyomtató, vagy egy virtuális egység(amelyet dokumentumonként állítanak be).

Az űrlap vezérlő elemek eddig ebben nem vettek részt, mindig az aktuális képernyő szerint formázták a szövegüket. Ennek következtében ha a vezérlő elem a szövegbe beillesztésre került , a dokumentum elrendezése megváltozott ha más eszközön néztük meg (nyomtatási kép, nyomtató, PDF export), de akkor is ha más nagyítás mellett néztük a képernyőn.

Mostantól, anem adatbeviteli űrlap vezérlőelemek szövegei (rádiógomb, címkék, jelölőnégyzetek, csoportpanel, nyomógombok) a dokumentum referencia egység beállításai szerint formázódnak, így biztosítva a jobb beilleszkedést a dokumentum szövegébe.

Ez a tulajdonság alkalmazásonként kapcsolható be, pontosabban modulonként. A felhasználói felületen keresztül ez nem állítható.

A konfigurációs beállításoknál a /org.openoffice.Office.Common/Forms/ControlLayout kiterjesztésre került, például a munkafüzeteknél, a …..../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics csomópont szabályozza azt, hogy a vezérlőelemek szöveg formázása bekapcsolt-e.

Alapértelmezettként a dokumentum referencia egysége bekapcsolt, a szöveges dokumentumoknál, rajzoknál, és bemutatóknál, és kikapcsolt az összes más dokumentum típusnál (munkafüzet, adatbázis űrlap, jelentés).

=== A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” ===
Az űrlapoknál a szöveg vezérlő elemek (szövegdoboz, stb.), mostantól támogatja a függőleges igazítást, amely eddig a nem szövegbevitelre használt más vezérlőelemeknél, mint például a címkék, eddig is rendelkezésre állt.

== [[Image:Szovegdoboz.PNG]] ==

== Jelentés tervező ==
=== Mező hozzáadása párbeszéd ablak elérhető a billentyűzetről is ===
A jelentés tervezőben a mező hozzáadása párbeszéd ablak a ALT+F8 gyorsbillentyűvel is elérhető.

[[Image:Rpt_mezo_hozzaad.PNG]]

== Tábla tervező ==
=== Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére ===
Mostantól lehetőség van új tulajdonság meghatározására drivers xcu fájlban. Alapértelmezettként engedélyezve van a MySQL (JDBC) és az Ado kapcsolatokra (beleértve az Access-t is, az Access esetében ez csak olvasható, nem változtatható meg).

Amikor ez engedélyezett, a tábla tervezőben látható az oszlopleírás a normál esetben látható leírás mellett, amely súgó szövegként működik. Az oszlopleírás felhasználásra kerül súgó szövegként ha a normál leírás üres, egyébként a normál leírás alkalmazódik.

[[Image:Kategoriak.PNG]]

File:Kategoriak.PNG

2010-08-19T07:24:37Z

R4zoli:

Base újdonságai a 3.3-s változatban

2010-08-19T07:23:34Z

R4zoli: /* Jelentés tervező */

File:Rpt mezo hozzaad.PNG

2010-08-19T07:22:52Z

R4zoli:

Base újdonságai a 3.3-s változatban

2010-08-19T07:22:11Z

R4zoli: /* A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” */

== Base általában ==
=== Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége ===
Új opció „Támogatja az elsődleges kulcsokat” az adatbázis kapcsolat „Speciális beállítások” alatt, ezzel lehetővé válik a Base által használt heurisztikus elsődleges kulcs felismerő algoritmusának felülbírálata.

Ez az új opció az ODBC, JDBC, és ADO adatbázis kapcsolatoknál érhető el.

[[Image:Spec_tul.PNG]]

Amikor adatbázishoz olyan általános csatolókon keresztül csatlakozunk, mint az ODBC, JDBC, vagy az ADO.A Base heurisztikus algoritmust használ, annak kiderítésére, hogy az adatbázis támogatja-e az elsődleges kulcsokat, mindezt azért, mert ezen csatolók egyike sem rendelkeznek specifikus támogatással ezen információ lekérdezésér.

Mivel a heurisztikus algoritmus néha hibázik, mostantól új opció „ Támogatja az elsődleges kulcsokat”, található a Szerkesztés>Speciális tulajdonságok>Speciális beállítások alatt. Az opció három állású jelölő négyzet, kijelölt állapot feltételezi az elsődleges kulcs támogatását, a kijelölés nélküli az elsődleges kulcs nem támogatott, a harmadik állapot a „nem meghatározott”, amelyik az alap beállított állapot, „alkalmazd a heurisztikus algoritmust” opciót jelenti.

Ne feledje ez csak azt jelenti, hogy a heurisztikus algoritmus alkalmazásának a felül írása. Ha bejelöli ezt, és az adatbázis nem támogatja az elsődleges kulcsokat, arra számíthat, hogy a Base hibajelzéseket küld vagy megfagy, mivel arra számít, hogy az elsődleges kulcsok támogatottak. Például ha elsődleges kulcsot próbál meg létrehozni a tábla tervezőben,

=== Csak olvasható adatbázis regisztrálásának támogatása ===
Mostantól a Base támogatja a csak olvasható adatbázisok regisztrálását.

Az adatbázis regisztrálására általában az Eszközök>Beállítások>OpenOffice.org Base>Adatbázisok alatt történik. A regisztrációs adatok az OpenOffice.org konfigurációs fájljaiban rögzítettek, ami azt is lehetővé teszi, hogy kiegészítő beállítások részenként is alkalmazhatók (kiterjesztéseken keresztül). Ha ezek a beállítási részek csak olvashatónak kerültek beállításra, a konfigurációs mechanizmuson keresztül, a felhasználói felület e beállításokat figyelembe veszi, nem engedélyezi a regisztrációs bejegyzés módosítását (szerkesztését, eltávolítását).

=== Adatbázis illesztő program kibővítése kiterjesztéssel ===
Részletes információ itt:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

A fenti specifikációból kivonat:

Az SDBC illesztő programok, kibővíthetők [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions kiterjesztésekkel].

A legtöbb illesztő program nem támogatja az olyan speciális tulajdonságokat, mint a nézetek szerkesztése, vagy a kulcsok hozzáadása vagy eldobása. Ezért az alábbi interfészek a kiterjesztés segítségével megvalósíthatók:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration] .

A szükséges tulajdonságok engedélyezésére a kiterjesztésben, az illesztő program konfigurációs bejegyzésének a kibővítésére van szükség. A konfigurációs bejegyzés ellenőrzésére a tulajdonságok bejegyzés alatt kerül sor, ha a szolgáltatás létrehozható a neve kerül felhasználásra. Az alábbiakban található a konfigurációs bejegyzés és a szolgáltatás név egyeztető táblázata:

Konfiguráció neve A megvalósítandó interfész neve

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

Annak engedélyezésére, hogy a fájl formátum specifikációban előírt helytől eltérő helyről is beolvasható legyen a lekérdezés, űrlap vagy jelentés, a kiterjesztés olyan szolgáltatást hozhat létre , amely az alábbi megnevezett interfészeket valósíthatja meg. A megnevezett konfigurációs bejegyzések:

* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier 

amelyek mindegyike az alabbi interfészeket kell, hogy megvalósítsa:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Űrlapok ==
=== Ctrl+F5 gyorsbillentyű ide-oda kapcsol a dokumentum és a legközelebbi vezérlő elem között ===
Ctrl+F5, amit korábban arra használtunk, hogy az első űrlapvezérlő elem kapja meg a fókuszt, ezt a legtöbb felhasználó nehezen értette meg,hogy miért így van, megváltozott.

Mostantól a kurzor pozícióhoz legközelebb álló vezérlőelemre áll ha az nincs a vezérlőelemben. Egyébként visszaadja a fókuszt a dokumentum nézetnek.

=== Az űrlap vezérlőelelmek az őket tartalmazó dokumentum szövegével megegyezően formázódnak ===
Ez az új tulajdonság nem kapcsolódik szorosan a Base-hez, de érdekes lehet.

A vezérlőelemek szövegének formázása megváltozott, igaz ez a változás csak néhány vezérlőelemre és néhány dokumentum típusra korlátozódik.

Az OOo alkalmazások a képernyőn látható szöveget általában az úgynevezett referencia egység beállításai szerint formázzák. Ez lehet a dokumentum részére kiválasztott nyomtató, vagy egy virtuális egység(amelyet dokumentumonként állítanak be).

Az űrlap vezérlő elemek eddig ebben nem vettek részt, mindig az aktuális képernyő szerint formázták a szövegüket. Ennek következtében ha a vezérlő elem a szövegbe beillesztésre került , a dokumentum elrendezése megváltozott ha más eszközön néztük meg (nyomtatási kép, nyomtató, PDF export), de akkor is ha más nagyítás mellett néztük a képernyőn.

Mostantól, anem adatbeviteli űrlap vezérlőelemek szövegei (rádiógomb, címkék, jelölőnégyzetek, csoportpanel, nyomógombok) a dokumentum referencia egység beállításai szerint formázódnak, így biztosítva a jobb beilleszkedést a dokumentum szövegébe.

Ez a tulajdonság alkalmazásonként kapcsolható be, pontosabban modulonként. A felhasználói felületen keresztül ez nem állítható.

A konfigurációs beállításoknál a /org.openoffice.Office.Common/Forms/ControlLayout kiterjesztésre került, például a munkafüzeteknél, a …..../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics csomópont szabályozza azt, hogy a vezérlőelemek szöveg formázása bekapcsolt-e.

Alapértelmezettként a dokumentum referencia egysége bekapcsolt, a szöveges dokumentumoknál, rajzoknál, és bemutatóknál, és kikapcsolt az összes más dokumentum típusnál (munkafüzet, adatbázis űrlap, jelentés).

=== A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” ===
Az űrlapoknál a szöveg vezérlő elemek (szövegdoboz, stb.), mostantól támogatja a függőleges igazítást, amely eddig a nem szövegbevitelre használt más vezérlőelemeknél, mint például a címkék, eddig is rendelkezésre állt.

== [[Image:Szovegdoboz.PNG]] ==

== Jelentés tervező ==
=== Mező hozzáadása párbeszéd ablak elérhető a billentyűzetről is ===
A jelentés tervezőben a mező hozzáadása párbeszéd ablak a ALT+F8 gyorsbillentyűvel is elérhető.

[[Image:]]

== Tábla tervező ==
=== Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére ===
Mostantól lehetőség van új tulajdonság meghatározására drivers xcu fájlban. Alapértelmezettként engedélyezve van a MySQL (JDBC) és az Ado kapcsolatokra (beleértve az Access-t is, az Access esetében ez csak olvasható, nem változtatható meg).

Amikor ez engedélyezett, a tábla tervezőben látható az oszlopleírás a normál esetben látható leírás mellett, amely súgó szövegként működik. Az oszlopleírás felhasználásra kerül súgó szövegként ha a normál leírás üres, egyébként a normál leírás alkalmazódik.

[[Image:]]

Base újdonságai a 3.3-s változatban

2010-08-19T07:21:43Z

R4zoli: /* Image: */

== Base általában ==
=== Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége ===
Új opció „Támogatja az elsődleges kulcsokat” az adatbázis kapcsolat „Speciális beállítások” alatt, ezzel lehetővé válik a Base által használt heurisztikus elsődleges kulcs felismerő algoritmusának felülbírálata.

Ez az új opció az ODBC, JDBC, és ADO adatbázis kapcsolatoknál érhető el.

[[Image:Spec_tul.PNG]]

Amikor adatbázishoz olyan általános csatolókon keresztül csatlakozunk, mint az ODBC, JDBC, vagy az ADO.A Base heurisztikus algoritmust használ, annak kiderítésére, hogy az adatbázis támogatja-e az elsődleges kulcsokat, mindezt azért, mert ezen csatolók egyike sem rendelkeznek specifikus támogatással ezen információ lekérdezésér.

Mivel a heurisztikus algoritmus néha hibázik, mostantól új opció „ Támogatja az elsődleges kulcsokat”, található a Szerkesztés>Speciális tulajdonságok>Speciális beállítások alatt. Az opció három állású jelölő négyzet, kijelölt állapot feltételezi az elsődleges kulcs támogatását, a kijelölés nélküli az elsődleges kulcs nem támogatott, a harmadik állapot a „nem meghatározott”, amelyik az alap beállított állapot, „alkalmazd a heurisztikus algoritmust” opciót jelenti.

Ne feledje ez csak azt jelenti, hogy a heurisztikus algoritmus alkalmazásának a felül írása. Ha bejelöli ezt, és az adatbázis nem támogatja az elsődleges kulcsokat, arra számíthat, hogy a Base hibajelzéseket küld vagy megfagy, mivel arra számít, hogy az elsődleges kulcsok támogatottak. Például ha elsődleges kulcsot próbál meg létrehozni a tábla tervezőben,

=== Csak olvasható adatbázis regisztrálásának támogatása ===
Mostantól a Base támogatja a csak olvasható adatbázisok regisztrálását.

Az adatbázis regisztrálására általában az Eszközök>Beállítások>OpenOffice.org Base>Adatbázisok alatt történik. A regisztrációs adatok az OpenOffice.org konfigurációs fájljaiban rögzítettek, ami azt is lehetővé teszi, hogy kiegészítő beállítások részenként is alkalmazhatók (kiterjesztéseken keresztül). Ha ezek a beállítási részek csak olvashatónak kerültek beállításra, a konfigurációs mechanizmuson keresztül, a felhasználói felület e beállításokat figyelembe veszi, nem engedélyezi a regisztrációs bejegyzés módosítását (szerkesztését, eltávolítását).

=== Adatbázis illesztő program kibővítése kiterjesztéssel ===
Részletes információ itt:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

A fenti specifikációból kivonat:

Az SDBC illesztő programok, kibővíthetők [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions kiterjesztésekkel].

A legtöbb illesztő program nem támogatja az olyan speciális tulajdonságokat, mint a nézetek szerkesztése, vagy a kulcsok hozzáadása vagy eldobása. Ezért az alábbi interfészek a kiterjesztés segítségével megvalósíthatók:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration] .

A szükséges tulajdonságok engedélyezésére a kiterjesztésben, az illesztő program konfigurációs bejegyzésének a kibővítésére van szükség. A konfigurációs bejegyzés ellenőrzésére a tulajdonságok bejegyzés alatt kerül sor, ha a szolgáltatás létrehozható a neve kerül felhasználásra. Az alábbiakban található a konfigurációs bejegyzés és a szolgáltatás név egyeztető táblázata:

Konfiguráció neve A megvalósítandó interfész neve

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

Annak engedélyezésére, hogy a fájl formátum specifikációban előírt helytől eltérő helyről is beolvasható legyen a lekérdezés, űrlap vagy jelentés, a kiterjesztés olyan szolgáltatást hozhat létre , amely az alábbi megnevezett interfészeket valósíthatja meg. A megnevezett konfigurációs bejegyzések:

* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier 

amelyek mindegyike az alabbi interfészeket kell, hogy megvalósítsa:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Űrlapok ==
=== Ctrl+F5 gyorsbillentyű ide-oda kapcsol a dokumentum és a legközelebbi vezérlő elem között ===
Ctrl+F5, amit korábban arra használtunk, hogy az első űrlapvezérlő elem kapja meg a fókuszt, ezt a legtöbb felhasználó nehezen értette meg,hogy miért így van, megváltozott.

Mostantól a kurzor pozícióhoz legközelebb álló vezérlőelemre áll ha az nincs a vezérlőelemben. Egyébként visszaadja a fókuszt a dokumentum nézetnek.

=== Az űrlap vezérlőelelmek az őket tartalmazó dokumentum szövegével megegyezően formázódnak ===
Ez az új tulajdonság nem kapcsolódik szorosan a Base-hez, de érdekes lehet.

A vezérlőelemek szövegének formázása megváltozott, igaz ez a változás csak néhány vezérlőelemre és néhány dokumentum típusra korlátozódik.

Az OOo alkalmazások a képernyőn látható szöveget általában az úgynevezett referencia egység beállításai szerint formázzák. Ez lehet a dokumentum részére kiválasztott nyomtató, vagy egy virtuális egység(amelyet dokumentumonként állítanak be).

Az űrlap vezérlő elemek eddig ebben nem vettek részt, mindig az aktuális képernyő szerint formázták a szövegüket. Ennek következtében ha a vezérlő elem a szövegbe beillesztésre került , a dokumentum elrendezése megváltozott ha más eszközön néztük meg (nyomtatási kép, nyomtató, PDF export), de akkor is ha más nagyítás mellett néztük a képernyőn.

Mostantól, anem adatbeviteli űrlap vezérlőelemek szövegei (rádiógomb, címkék, jelölőnégyzetek, csoportpanel, nyomógombok) a dokumentum referencia egység beállításai szerint formázódnak, így biztosítva a jobb beilleszkedést a dokumentum szövegébe.

Ez a tulajdonság alkalmazásonként kapcsolható be, pontosabban modulonként. A felhasználói felületen keresztül ez nem állítható.

A konfigurációs beállításoknál a /org.openoffice.Office.Common/Forms/ControlLayout kiterjesztésre került, például a munkafüzeteknél, a …..../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics csomópont szabályozza azt, hogy a vezérlőelemek szöveg formázása bekapcsolt-e.

Alapértelmezettként a dokumentum referencia egysége bekapcsolt, a szöveges dokumentumoknál, rajzoknál, és bemutatóknál, és kikapcsolt az összes más dokumentum típusnál (munkafüzet, adatbázis űrlap, jelentés).

=== A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” ===
Az űrlapoknál a szöveg vezérlő elemek (szövegdoboz, stb.), mostantól támogatja a függőleges igazítást, amely eddig a nem szövegbevitelre használt más vezérlőelemeknél, mint például a címkék, eddig is rendelkezésre állt.

== [[Image:Szovegdoboz.PNG]] ==

== Jelentés tervező ==
=== Mező hozzáadása párbeszéd ablak elérhető a billentyűzetről is ===
A jelentés tervezőben a mező hozzáadása párbeszéd ablak a ALT+F8 gyorsbillentyűvel is elérhető.

[[Image:]]

== Tábla tervező ==
=== Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére ===
Mostantól lehetőség van új tulajdonság meghatározására drivers xcu fájlban. Alapértelmezettként engedélyezve van a MySQL (JDBC) és az Ado kapcsolatokra (beleértve az Access-t is, az Access esetében ez csak olvasható, nem változtatható meg).

Amikor ez engedélyezett, a tábla tervezőben látható az oszlopleírás a normál esetben látható leírás mellett, amely súgó szövegként működik. Az oszlopleírás felhasználásra kerül súgó szövegként ha a normál leírás üres, egyébként a normál leírás alkalmazódik.

[[Image:]]

File:Szovegdoboz.PNG

2010-08-19T07:20:50Z

R4zoli:

Base újdonságai a 3.3-s változatban

2010-08-19T07:18:43Z

R4zoli: /* Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége */

== Base általában ==
=== Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége ===
Új opció „Támogatja az elsődleges kulcsokat” az adatbázis kapcsolat „Speciális beállítások” alatt, ezzel lehetővé válik a Base által használt heurisztikus elsődleges kulcs felismerő algoritmusának felülbírálata.

Ez az új opció az ODBC, JDBC, és ADO adatbázis kapcsolatoknál érhető el.

[[Image:Spec_tul.PNG]]

Amikor adatbázishoz olyan általános csatolókon keresztül csatlakozunk, mint az ODBC, JDBC, vagy az ADO.A Base heurisztikus algoritmust használ, annak kiderítésére, hogy az adatbázis támogatja-e az elsődleges kulcsokat, mindezt azért, mert ezen csatolók egyike sem rendelkeznek specifikus támogatással ezen információ lekérdezésér.

Mivel a heurisztikus algoritmus néha hibázik, mostantól új opció „ Támogatja az elsődleges kulcsokat”, található a Szerkesztés>Speciális tulajdonságok>Speciális beállítások alatt. Az opció három állású jelölő négyzet, kijelölt állapot feltételezi az elsődleges kulcs támogatását, a kijelölés nélküli az elsődleges kulcs nem támogatott, a harmadik állapot a „nem meghatározott”, amelyik az alap beállított állapot, „alkalmazd a heurisztikus algoritmust” opciót jelenti.

Ne feledje ez csak azt jelenti, hogy a heurisztikus algoritmus alkalmazásának a felül írása. Ha bejelöli ezt, és az adatbázis nem támogatja az elsődleges kulcsokat, arra számíthat, hogy a Base hibajelzéseket küld vagy megfagy, mivel arra számít, hogy az elsődleges kulcsok támogatottak. Például ha elsődleges kulcsot próbál meg létrehozni a tábla tervezőben,

=== Csak olvasható adatbázis regisztrálásának támogatása ===
Mostantól a Base támogatja a csak olvasható adatbázisok regisztrálását.

Az adatbázis regisztrálására általában az Eszközök>Beállítások>OpenOffice.org Base>Adatbázisok alatt történik. A regisztrációs adatok az OpenOffice.org konfigurációs fájljaiban rögzítettek, ami azt is lehetővé teszi, hogy kiegészítő beállítások részenként is alkalmazhatók (kiterjesztéseken keresztül). Ha ezek a beállítási részek csak olvashatónak kerültek beállításra, a konfigurációs mechanizmuson keresztül, a felhasználói felület e beállításokat figyelembe veszi, nem engedélyezi a regisztrációs bejegyzés módosítását (szerkesztését, eltávolítását).

=== Adatbázis illesztő program kibővítése kiterjesztéssel ===
Részletes információ itt:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

A fenti specifikációból kivonat:

Az SDBC illesztő programok, kibővíthetők [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions kiterjesztésekkel].

A legtöbb illesztő program nem támogatja az olyan speciális tulajdonságokat, mint a nézetek szerkesztése, vagy a kulcsok hozzáadása vagy eldobása. Ezért az alábbi interfészek a kiterjesztés segítségével megvalósíthatók:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration] .

A szükséges tulajdonságok engedélyezésére a kiterjesztésben, az illesztő program konfigurációs bejegyzésének a kibővítésére van szükség. A konfigurációs bejegyzés ellenőrzésére a tulajdonságok bejegyzés alatt kerül sor, ha a szolgáltatás létrehozható a neve kerül felhasználásra. Az alábbiakban található a konfigurációs bejegyzés és a szolgáltatás név egyeztető táblázata:

Konfiguráció neve A megvalósítandó interfész neve

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

Annak engedélyezésére, hogy a fájl formátum specifikációban előírt helytől eltérő helyről is beolvasható legyen a lekérdezés, űrlap vagy jelentés, a kiterjesztés olyan szolgáltatást hozhat létre , amely az alábbi megnevezett interfészeket valósíthatja meg. A megnevezett konfigurációs bejegyzések:

* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier 

amelyek mindegyike az alabbi interfészeket kell, hogy megvalósítsa:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Űrlapok ==
=== Ctrl+F5 gyorsbillentyű ide-oda kapcsol a dokumentum és a legközelebbi vezérlő elem között ===
Ctrl+F5, amit korábban arra használtunk, hogy az első űrlapvezérlő elem kapja meg a fókuszt, ezt a legtöbb felhasználó nehezen értette meg,hogy miért így van, megváltozott.

Mostantól a kurzor pozícióhoz legközelebb álló vezérlőelemre áll ha az nincs a vezérlőelemben. Egyébként visszaadja a fókuszt a dokumentum nézetnek.

=== Az űrlap vezérlőelelmek az őket tartalmazó dokumentum szövegével megegyezően formázódnak ===
Ez az új tulajdonság nem kapcsolódik szorosan a Base-hez, de érdekes lehet.

A vezérlőelemek szövegének formázása megváltozott, igaz ez a változás csak néhány vezérlőelemre és néhány dokumentum típusra korlátozódik.

Az OOo alkalmazások a képernyőn látható szöveget általában az úgynevezett referencia egység beállításai szerint formázzák. Ez lehet a dokumentum részére kiválasztott nyomtató, vagy egy virtuális egység(amelyet dokumentumonként állítanak be).

Az űrlap vezérlő elemek eddig ebben nem vettek részt, mindig az aktuális képernyő szerint formázták a szövegüket. Ennek következtében ha a vezérlő elem a szövegbe beillesztésre került , a dokumentum elrendezése megváltozott ha más eszközön néztük meg (nyomtatási kép, nyomtató, PDF export), de akkor is ha más nagyítás mellett néztük a képernyőn.

Mostantól, anem adatbeviteli űrlap vezérlőelemek szövegei (rádiógomb, címkék, jelölőnégyzetek, csoportpanel, nyomógombok) a dokumentum referencia egység beállításai szerint formázódnak, így biztosítva a jobb beilleszkedést a dokumentum szövegébe.

Ez a tulajdonság alkalmazásonként kapcsolható be, pontosabban modulonként. A felhasználói felületen keresztül ez nem állítható.

A konfigurációs beállításoknál a /org.openoffice.Office.Common/Forms/ControlLayout kiterjesztésre került, például a munkafüzeteknél, a …..../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics csomópont szabályozza azt, hogy a vezérlőelemek szöveg formázása bekapcsolt-e.

Alapértelmezettként a dokumentum referencia egysége bekapcsolt, a szöveges dokumentumoknál, rajzoknál, és bemutatóknál, és kikapcsolt az összes más dokumentum típusnál (munkafüzet, adatbázis űrlap, jelentés).

=== A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” ===
Az űrlapoknál a szöveg vezérlő elemek (szövegdoboz, stb.), mostantól támogatja a függőleges igazítást, amely eddig a nem szövegbevitelre használt más vezérlőelemeknél, mint például a címkék, eddig is rendelkezésre állt.

== [[Image:]] ==
== Jelentés tervező ==
=== Mező hozzáadása párbeszéd ablak elérhető a billentyűzetről is ===
A jelentés tervezőben a mező hozzáadása párbeszéd ablak a ALT+F8 gyorsbillentyűvel is elérhető.

[[Image:]]

== Tábla tervező ==
=== Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére ===
Mostantól lehetőség van új tulajdonság meghatározására drivers xcu fájlban. Alapértelmezettként engedélyezve van a MySQL (JDBC) és az Ado kapcsolatokra (beleértve az Access-t is, az Access esetében ez csak olvasható, nem változtatható meg).

Amikor ez engedélyezett, a tábla tervezőben látható az oszlopleírás a normál esetben látható leírás mellett, amely súgó szövegként működik. Az oszlopleírás felhasználásra kerül súgó szövegként ha a normál leírás üres, egyébként a normál leírás alkalmazódik.

[[Image:]]

File:Spec tul.PNG

2010-08-19T07:17:42Z

R4zoli:

Base újdonságai a 3.3-s változatban

2010-08-19T07:16:50Z

R4zoli: Created page with '== Base általában == === Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége === Új opció „Támogatja az elsődleges kulcsokat…'

== Base általában ==
=== Elsődleges kulcs felismerő heurisztikus algoritmus felülbírálatának engedélyezhetősége ===
Új opció „Támogatja az elsődleges kulcsokat” az adatbázis kapcsolat „Speciális beállítások” alatt, ezzel lehetővé válik a Base által használt heurisztikus elsődleges kulcs felismerő algoritmusának felülbírálata.

Ez az új opció az ODBC, JDBC, és ADO adatbázis kapcsolatoknál érhető el.

[[Image:]]

Amikor adatbázishoz olyan általános csatolókon keresztül csatlakozunk, mint az ODBC, JDBC, vagy az ADO.A Base heurisztikus algoritmust használ, annak kiderítésére, hogy az adatbázis támogatja-e az elsődleges kulcsokat, mindezt azért, mert ezen csatolók egyike sem rendelkeznek specifikus támogatással ezen információ lekérdezésér.

Mivel a heurisztikus algoritmus néha hibázik, mostantól új opció „ Támogatja az elsődleges kulcsokat”, található a Szerkesztés>Speciális tulajdonságok>Speciális beállítások alatt. Az opció három állású jelölő négyzet, kijelölt állapot feltételezi az elsődleges kulcs támogatását, a kijelölés nélküli az elsődleges kulcs nem támogatott, a harmadik állapot a „nem meghatározott”, amelyik az alap beállított állapot, „alkalmazd a heurisztikus algoritmust” opciót jelenti.

Ne feledje ez csak azt jelenti, hogy a heurisztikus algoritmus alkalmazásának a felül írása. Ha bejelöli ezt, és az adatbázis nem támogatja az elsődleges kulcsokat, arra számíthat, hogy a Base hibajelzéseket küld vagy megfagy, mivel arra számít, hogy az elsődleges kulcsok támogatottak. Például ha elsődleges kulcsot próbál meg létrehozni a tábla tervezőben,

=== Csak olvasható adatbázis regisztrálásának támogatása ===
Mostantól a Base támogatja a csak olvasható adatbázisok regisztrálását.

Az adatbázis regisztrálására általában az Eszközök>Beállítások>OpenOffice.org Base>Adatbázisok alatt történik. A regisztrációs adatok az OpenOffice.org konfigurációs fájljaiban rögzítettek, ami azt is lehetővé teszi, hogy kiegészítő beállítások részenként is alkalmazhatók (kiterjesztéseken keresztül). Ha ezek a beállítási részek csak olvashatónak kerültek beállításra, a konfigurációs mechanizmuson keresztül, a felhasználói felület e beállításokat figyelembe veszi, nem engedélyezi a regisztrációs bejegyzés módosítását (szerkesztését, eltávolítását).

=== Adatbázis illesztő program kibővítése kiterjesztéssel ===
Részletes információ itt:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

A fenti specifikációból kivonat:

Az SDBC illesztő programok, kibővíthetők [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions kiterjesztésekkel].

A legtöbb illesztő program nem támogatja az olyan speciális tulajdonságokat, mint a nézetek szerkesztése, vagy a kulcsok hozzáadása vagy eldobása. Ezért az alábbi interfészek a kiterjesztés segítségével megvalósíthatók:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration] .

A szükséges tulajdonságok engedélyezésére a kiterjesztésben, az illesztő program konfigurációs bejegyzésének a kibővítésére van szükség. A konfigurációs bejegyzés ellenőrzésére a tulajdonságok bejegyzés alatt kerül sor, ha a szolgáltatás létrehozható a neve kerül felhasználásra. Az alábbiakban található a konfigurációs bejegyzés és a szolgáltatás név egyeztető táblázata:

Konfiguráció neve A megvalósítandó interfész neve

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

Annak engedélyezésére, hogy a fájl formátum specifikációban előírt helytől eltérő helyről is beolvasható legyen a lekérdezés, űrlap vagy jelentés, a kiterjesztés olyan szolgáltatást hozhat létre , amely az alábbi megnevezett interfészeket valósíthatja meg. A megnevezett konfigurációs bejegyzések:

* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier 

amelyek mindegyike az alabbi interfészeket kell, hogy megvalósítsa:

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Űrlapok ==
=== Ctrl+F5 gyorsbillentyű ide-oda kapcsol a dokumentum és a legközelebbi vezérlő elem között ===
Ctrl+F5, amit korábban arra használtunk, hogy az első űrlapvezérlő elem kapja meg a fókuszt, ezt a legtöbb felhasználó nehezen értette meg,hogy miért így van, megváltozott.

Mostantól a kurzor pozícióhoz legközelebb álló vezérlőelemre áll ha az nincs a vezérlőelemben. Egyébként visszaadja a fókuszt a dokumentum nézetnek.

=== Az űrlap vezérlőelelmek az őket tartalmazó dokumentum szövegével megegyezően formázódnak ===
Ez az új tulajdonság nem kapcsolódik szorosan a Base-hez, de érdekes lehet.

A vezérlőelemek szövegének formázása megváltozott, igaz ez a változás csak néhány vezérlőelemre és néhány dokumentum típusra korlátozódik.

Az OOo alkalmazások a képernyőn látható szöveget általában az úgynevezett referencia egység beállításai szerint formázzák. Ez lehet a dokumentum részére kiválasztott nyomtató, vagy egy virtuális egység(amelyet dokumentumonként állítanak be).

Az űrlap vezérlő elemek eddig ebben nem vettek részt, mindig az aktuális képernyő szerint formázták a szövegüket. Ennek következtében ha a vezérlő elem a szövegbe beillesztésre került , a dokumentum elrendezése megváltozott ha más eszközön néztük meg (nyomtatási kép, nyomtató, PDF export), de akkor is ha más nagyítás mellett néztük a képernyőn.

Mostantól, anem adatbeviteli űrlap vezérlőelemek szövegei (rádiógomb, címkék, jelölőnégyzetek, csoportpanel, nyomógombok) a dokumentum referencia egység beállításai szerint formázódnak, így biztosítva a jobb beilleszkedést a dokumentum szövegébe.

Ez a tulajdonság alkalmazásonként kapcsolható be, pontosabban modulonként. A felhasználói felületen keresztül ez nem állítható.

A konfigurációs beállításoknál a /org.openoffice.Office.Common/Forms/ControlLayout kiterjesztésre került, például a munkafüzeteknél, a …..../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics csomópont szabályozza azt, hogy a vezérlőelemek szöveg formázása bekapcsolt-e.

Alapértelmezettként a dokumentum referencia egysége bekapcsolt, a szöveges dokumentumoknál, rajzoknál, és bemutatóknál, és kikapcsolt az összes más dokumentum típusnál (munkafüzet, adatbázis űrlap, jelentés).

=== A szöveg (jellegű) űrlap vezérlő elemeknél új tulajdonság „Függőleges igazítás” ===
Az űrlapoknál a szöveg vezérlő elemek (szövegdoboz, stb.), mostantól támogatja a függőleges igazítást, amely eddig a nem szövegbevitelre használt más vezérlőelemeknél, mint például a címkék, eddig is rendelkezésre állt.

== [[Image:]] ==
== Jelentés tervező ==
=== Mező hozzáadása párbeszéd ablak elérhető a billentyűzetről is ===
A jelentés tervezőben a mező hozzáadása párbeszéd ablak a ALT+F8 gyorsbillentyűvel is elérhető.

[[Image:]]

== Tábla tervező ==
=== Az adatbázis csatolók új metaadat csomópontja az adatbázis oszlopleírások megtekintésére ===
Mostantól lehetőség van új tulajdonság meghatározására drivers xcu fájlban. Alapértelmezettként engedélyezve van a MySQL (JDBC) és az Ado kapcsolatokra (beleértve az Access-t is, az Access esetében ez csak olvasható, nem változtatható meg).

Amikor ez engedélyezett, a tábla tervezőben látható az oszlopleírás a normál esetben látható leírás mellett, amely súgó szövegként működik. Az oszlopleírás felhasználásra kerül súgó szövegként ha a normál leírás üres, egyébként a normál leírás alkalmazódik.

[[Image:]]

Kezdőlap

2010-08-19T07:13:22Z

R4zoli: /* Az OpenOffice.org 3.2 újdonságai */

== Üdvözli az OpenOffice.org wiki ==
A wiki az OpenOffice.org (OOo) felhasználóinak / fejlesztőinek készült. A felhasználók egyre növekvő száma is szükségessé tesz a [http://hu.openoffice.org magyar OOo honlapon] kívüli információforrást.
Az itt található linkekre kattintva közvetlenül eljuthat a kiválasztott oldalra.

Csatlakozzon az OpenOffice.org wiki készítőihez. Lehetőleg használja az OOo bejelentkezési nevét a regisztrációjakor. (A későbbiekben összevonásra kerülhet a két rész.) Néhány funkciót csak a bejelentkezett felhasználók használhatnak, a spamelés elkerülésére. A regisztráció része a levelezési cím ellenőrzése.

== Fórumok ==
Az alábbi fórumokon választ kaphat a feltett kérdésére, kereshet a korábbi témák között.

Magyar nyelven:
[http://user.services.openoffice.org/hu/forum/ OpenOffice.org Közösségi Fórum]

Valamint a:
[http://hup.hu/forum/192 HUP iroda fórum]

Angolul:
[http://user.services.openoffice.org/en/forum/ OpenOffice.org Community Forum]

----
== Az OpenOffice.org 3.3 újdonságai ==
[[Base újdonságai a 3.3-s változatban]]
== Az OpenOffice.org 3.2 újdonságai ==
[[Base újdonságai a 3.2-s változatban]]

== Az OpenOffice.org 3.1 újdonságai ==
[http://www.openoffice.hu/2009/05/az-openoffice-31-ujdonsagai/ Az OpenOffice.org 3.1 újdonságai]

[[Base újdonságai a 3.1-s változatban]]

== Az OpenOffice.org 3.0 újdonságai ==
[http://hu.openoffice.org/files/documents/176/4324/OpenOffice.org3_ujdonsagai.pdf 3.0 újdonságai]

== Az OpenOffice.org 2.4 újdonságai ==
[[2.4 változat újdonságai]]

== Dokumentáció ==

Az OpenOffice.org használatával kapcsolatos dokumentációk ebben a wikiben:

[[HU/Documentation/BASIC_Guide|OpenOffice.org BASIC programozói útmutató]]

== Fejlesztés ==
Az OpenOffice.org magyar fejlesztésével kapcsolatos oldalak.

[[Hu.openoffice.org/Magyar_Ispell_hibabejelent%C3%A9s|Magyar Ispell hibabejelentés]]

[[Hu.openoffice.org/Szabad_diploma_-_OOo|Szabad diploma - OOo]]

[[Hu.openoffice.org/Minőségbiztosítás|Minőségbiztosítás - VCLTesttool]]

{{InterWiki Languages}}

[[Category:Magyar]]

Base/New features in 3 3

2010-07-09T09:59:01Z

R4zoli: /* Text(-like) input form controls also support the "Vertical Alignment" property */

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:Vert_alignment.png]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:Add_field.png]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:Col_description.PNG]]

File:Vert alignment.png

2010-07-09T09:58:35Z

R4zoli: new form control property in OOo 3.3 vertical alignment

new form control property in OOo 3.3 vertical alignment

Base/New features in 3 3

2010-07-09T09:57:23Z

R4zoli: /* New MetaData node for Database drivers to view column descriptions from the database */

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:Add_field.png]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:Col_description.PNG]]

File:Col description.PNG

2010-07-09T09:56:53Z

R4zoli: new columns description in Base table design view

new columns description in Base table design view

Base/New features in 3 3

2010-07-09T09:55:36Z

R4zoli: /* Add Field dialog now accessible via keyboard */

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:Add_field.png]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:]]

File:Add field.png

2010-07-09T09:55:02Z

R4zoli: add field as shortcut in report designer

add field as shortcut in report designer

Base/New features in 3 3

2010-07-09T09:52:54Z

R4zoli: Created page with '= New features in OOo 3.3 Base = == Base in general == New features "under the hood" === Allow to overrule Base's heuristics for primary key support === There's a new option "Su…'

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:]]

Database

2010-07-09T09:48:10Z

R4zoli: /* General */

{{Database/Lang|Database}}
This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add missing documents to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting Started with Base)
: [http://documentation.openoffice.org/manuals/oooauthors2/0110GS-GettingStartedWithBase.pdf Getting Started with Base] - ''PDF''
: or Getting Started with Base [http://wiki.services.openoffice.org/wiki/Documentation/OOo3_User_Guides/Getting_Started/Getting_Started_with_Base wiki version]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* Base Guide
:[http://wiki.services.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Base_Guide/Planning Base Guide Planning]
:Base Guide Outline Proposal from OOoAuthors

* OpenOffice.org Base Manual
: [http://nothickmanuals.info/doku.php/articles:ooobaseprimer OpenOffice.org Base Primer]
: Initial Authors: Andrew 'Drew' Jensen, Frank Schoenheit, et al.
: A short screenshot-guided overview on how to use Base.

* Mid Level Base Tutorial
: [http://documentation.openoffice.org/servlets/ProjectDocumentList?folderID=778&expandFolder=778&folderID=597 Mid Level Base Tutorial]
: Innitial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"- From getting started to more advanced
: [http://sheepdogguides.com/fdb/fdb1main.htm Tutorials and "How to"s... 45 from one author at Sheepdogguides.com]
: Initial author: TK Boyd
: Both specific tasks and fundamental skills are explained.
: A section introducing the use of macros added 5/09.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.2
: [[Base/New_features_in_3_2|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

* New Features in 3.3
: [[Base/New_features_in_3_3|New Features]]
: Initial author: Reizinger Zoltán
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description followed''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
*FAQ (Base)
: [[FAQ_(Base)|FAQ_(Base)]]

* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

* Using csv/text files as editable data source.
: [http://user.services.openoffice.org/en/forum/viewtopic.php?f=83&t=23260 OOo users forum Tutorial]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

* Three table example, with supporting essay- Project management
: [http://sheepdogguides.com/fdb/fdb7peopproj.htm Link to essay, which has link to download a small database]
: The database illustrates techniques explained in the essay. It is provided as an illustration, not for the data it contains.

* Base Example
: [[File:DerbyToursDB.odb]]
: [[User:HCPotter]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the corresponding links.

*[[FR/Documentation/HSQLDB Guide]]
*[[FR/Documentation/Base/Nouvelles Fonctions 3 1]]

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

* [[OpenOffice_per_JDBC_an_Informix | Anbindung von OpenOffice an Informix per JDBC]]

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]
[[Category:Project]]

SUN Report Builder/Functions

2010-05-11T11:50:34Z

R4zoli:

[[fr:FR/Documentation/Base/Rapports/Fonctions]]
{{Database/Lang|Base/Reports/Functions}}

'''Date/Time''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| DATE
| Provides an internal number for the date given.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| month
| An integer between 1 and 12 representing the month.
|-
| day
| An integer between 1 and 31 representing the day of the month.
|}

|
|-
| DATEDIF
| Returns the number of years, months, or days between two dates.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| EndDate
| Second date.
|-
| Format
| Format code.
|}

|
|-
| DATEVALUE
| Returns an internal number for a text having a possible date format.
|
|-
| DAY
| Returns the sequential date of the month as an integer (1-31) in relation to the date value.
|
|-
| DAYS
| Calculates the number of days between two dates.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| Date_1
| The start date for calculating the difference in days.
|}

|
|-
| HOUR
| Determines the sequential number of the hour of the day (0-23) for the time value.
|
|-
| MINUTE
| Determines the sequential number for the minute of the hour (0-59) for the time value.
|
|-
| MONTH
| Determines the sequential number of a month of the year (1-12) for the date value.
|
|-
| NOW
| Determines the current time of the computer.
|
|-
| SECOND
| Determines the sequential number of the second of a minute (0-59) for the time value.
|
|-
| TIME
| Determines a time value from the details for hour, minute and second.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| minute
| The integer for the minute.
|-
| second
| The integer for the second.
|}

|
|-
| TIMEVALUE
| Returns a sequential number for a text shown in a possible time entry format.
|
|-
| TODAY
| Determines the current date of the computer.
|
|-
| WEEKDAY
| Returns the day of the week for the date value as an integer (1-7).
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| Type
| Fixes the beginning of the week and the type of calculation to be used.(1 = Sunday is the first day of the week, with value 1; Saturday has value 7, 2 = Monday is the first day of the week, with value 1; Sunday has value 7, 3 = Monday is the first day of the week, with value 0; Sunday has value 6)
|}

|
|-
| YEAR
| Returns the year of a date value as an integer.
|
|}

 '''Mathematical''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| ABS
| Absolute value of a number.
|
|-
| AVERAGE
| Returns the average of a sample.
|
|-
| AVERAGE
| Returns the average of a sample.
|
|-
| EVEN
| Rounds a positive number up and negative number down to the nearest even integer.
|
|-
| MAX
| Returns the maximum value in a list of arguments.
|
|-
| MAXA
| Returns the maximum value in a list of arguments. Text is evaluated as zero.
|
|-
| MIN
| Returns the minimum value in a list of arguments.
|
|-
| MINA
| Returns the smallest value in a list of arguments. Text is evaluated as zero.
|
|-
| MOD
| Calculates the remainder of a division.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| Divisor
| The number by which the dividend is divided.
|}

|
|-
| ODD
| Rounds a positive number up and negative number down to the nearest odd integer.
|
|-
| SUM
| Returns the sum of all arguments.
|
|}

 '''Logical''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| AND
| Returns TRUE if all arguments are TRUE.
|
|-
| FALSE
| Defines the logical value as FALSE.
|
|-
| IF
| Specifies a logical test to be performed.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| Then_value
| The result of the function if the logical test returns a TRUE.
|-
| Otherwise_value
| The result of the function if the logical test returns FALSE.
|}

|
|-
| NOT
| Reverses the value of the argument.
|
|-
| OR
| Returns TRUE if an argument is TRUE.
|
|-
| TRUE
| Returns the logical value TRUE.
|
|-
| XOR
| Returns TRUE if a odd number of arguments are TRUE.
|
|}

 '''Information''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| CHOOSE
| Selects a value from a list of up to 30 value arguments.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| value
| Value 1, value 2,... The list of arguments from which a value is chosen.
|}

|
|-
| COUNT
| Counts how many numbers are in the list of arguments.
|
|-
| COUNTA
| Counts how many values are in the list of arguments.
|
|-
| COUNTBLANK
| Counts the blank cells in a specified range.
|
|-
| HASCHANGED
| Checks whether the columns specified by the given names has changed. Place a column name between double quotes.
|
|-
| ISBLANK
| Returns TRUE if value refers to an empty cell.
|
|-
| ISERR
| Returns TRUE if the value is an error value not equal to #N/A.
|
|-
| ISERROR
| Returns TRUE if the value is an error value.
|
|-
| ISEVEN
| Returns TRUE if value is an even integer.
|
|-
| ISLOGICAL
| Returns TRUE if the value carries a logical number format.
|
|-
| ISNA
| Returns TRUE if value equals #N/A.
|
|-
| ISNONTEXT
| Returns TRUE if the value is not text.
|
|-
| ISNUMBER
| Returns TRUE if value is a number.
|
|-
| ISODD
| Returns TRUE if value is an odd integer.
|
|-
| ISREF
| Returns TRUE if value is a reference.
|
|-
| ISTEXT
| Returns TRUE if value is text.
|
|-
| NA
| Not available. Returns the error value #N/A.
|
|}

 '''User-Defined''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| NULL
| Returns a NULL-Value
|
|}

 '''Text''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| EXACT
| Specifies whether two texts are identical.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| text_2
| The second text for comparing texts.
|}

|
|-
| FIND
| Looks for a string of text within another (case sensitive)
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| text
| The text in which a search is to be made.
|-
| position
| The position in the text from which the search starts.
|}

|
|-
| LEFT
| Returns the first character or characters of a text.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| number
| The number of characters for the start text.
|}

|
|-
| LEN
| Calculates length of a text string.
|
|-
| LOWER
| Converts text to lowercase.
|
|-
| MID
| Returns a partial text string of a text.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| start
| The position from which the part word is to be determined.
|-
| number
| The number of characters for the text.
|}

|
|-
| REPLACE
| Replaces characters within a text string with a different text string.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| position
| The character position from which text is to be replaced.
|-
| length
| The number of characters to be replaced.
|-
| new text
| The text to be inserted.
|}

|
|-
| REPT
| Repeats text a given number of times.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| number
| The number of times the text is to be repeated.
|}

|
|-
| RIGHT
| Returns the last character or characters of a text.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| number
| The number of characters for the end text.
|}

|
|-
| SUBSTITUTE
| Substitutes new text for old text in a string.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| search_text
| The partial string to be (repeatedly) replaced.
|-
| new text
| The text which is to replace the text string.
|-
| occurrence
| Which occurence of the old text is to be replaced.
|}

|
|-
| T
| Converts a value into text.
|
|-
| TEXT
| Converts a number to text according to a given format.
|
|-
| TRIM
| Removes extra spaces from text.
|
|-
| UNICHAR
| Converts a code number into a Unicode character or letter.
|
|-
| UNICODE
| Returns the numeric code for the first Unicode character in a text string.
|
|-
| UPPER
| Converts text to uppercase.
|
|-
| URLENCODE
| Applies URL-Encoding to a text given in the first parameter using the encoding specified in the second parameter. If no encoding is given, ISO-8859-1 is assumed.
{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Parameter Name'''''
| '''''Parameter Description'''''
|-
| Encoding
| The Encoding to be used.
|}

|
|}

CONCAT or CONCATENATE functions not supported, but you can use [Textfieldname]&" "&[Textfieldname] to concatenate text fields.

 '''Rounding''' 

{| cellpadding="10" border="1" class="prettytable"
|-
| '''''Function Name'''''
| '''''Description'''''
| '''''Example'''''
|-
| INT
| Rounds a number down to the nearest integer.
|
|}

 
[[Category:Database]] [[Category:Extensions]]