[Solved] Labels from an existing calc spread sheet

[ptownpapa]

In Excel I could create a spreadsheet and use Word to extract the info and print it as labels...
Open Office seems to demand a Data base??
Please advise..

[RusselB]

Technically this is a database process, and even in Excel/Word the functionality is based on how a database works.
You can import a spreadsheet into Writer and then use the Mail Merge options (which I'm guessing is what you are actually after).
If my guess is wrong, please advise us as to what you are trying to do.

[Villeroy]

menu:File>New>Labels...

[Villeroy]

If the label wizard does not work for you or if you want to use a template downloaded from the label vendor, then it is easy enough to do it manually.
It involves 3 files:
1. a tabular source which is a spreadsheet in many cases but could be a lot more than that.
2. a Base document connected to the source
3. a label document (Writer) with the right layout. The wizard produces tiles of frames. Downloaded templates consist of one table with the right spacing.

Having these files, you can design one label with text, pictures and place holders, append a [Next Record] field and copy this label across the other labels. Save the text document with place holders as a template so you don't have to do anything when you need this layout again.

Here is a description, discussion and an example based on a data source and Base document we all have on our systems since it is installed with the office suite: viewtopic.php?f=29&t=87966&p=423345#p423345

[ptownpapa]

Thank you to all those who tried to help..... I read the manual (several times - Reflect and interpret) and found I had to register a Database, create a Table, Copy the existing spreadsheet into the Table, and then interpret the printing instructions. At the end I could do what took 10 minutes in MS Word with no manual. I still like Open Office - no MS BS and there is actually a helpful forum for the unwashed. Again - Thank you all

[Villeroy]

No, you don't have to create a new database and copy data to it.
You can connect a spreadsheet to a database document.

File>New>Database...
[X] Connect to existing database
Type: "Spreadsheet"
[X] Register the database
Save the database.

Now you have the used areas of all sheets represented as tables of a pseudo-database. Nothing has been copied nor imported nor converted. Your data are still in the spreadsheet and Base represents those data as if your spreadsheet were a database. This pseudo-database is read-only and any changes to the spreadsheet require a restart of the office suite before the database connection reflects the changes.
Since spreadsheets are free hand tools, not even close to databases, you may want to define cell ranges as database ranges in Calc via menu:Data>Define... These lists appear as separate database tables when the sheet contains more than just the list data. Then you can hide away all unwanted pseudo-tables in Base via menu:Tools>Table Filter... Unelected tables will be hidden.

[ptownpapa]

I missed that in the manual.... Thank you.

[ptownpapa]

I have reread all of the answers... none offered the quick fix you just handed me - now I know a bit more then before.
John

[John_Ha]

You need three files for labels:

1 A spreadsheet .ods file with the data
2 A database .odb file which has nothing in it but which is registered and can be considered to be the "interface between the document and the spreadsheet"
3 A document .odt file for the labels.

If you do not have the .odb file in Step 2, or if you have not registered it, it will not work.

I wrote this aide-memoire as a post on another forum many, many years ago. It was based on OOo v2, used a .xls file, is out of date and it isn't fully correct ... but it serves me well each Christmas.

[Villeroy]

I wrote this aide-memoire as a post on another forum many, many years ago. It was based on OOo v2, used a .xls file, is out of date and it isn't fully correct ... but it serves me well each Christmas.

In other words: You need one text document for every layout of labels (3x7, 2x8, different sizes etc) and the source sheets need to be reloaded after editing. I use to recommend reloading the whole office suite just to be sure.
BUT you only need one registered data source (*.odb) and one spreadsheet document keeping the list. Every placeholder in your text documents refers to DatabaseName.TableName.ColumnName. When any of the 3 names changes in the data source, some placeholder field can not be filled with data anymore.

When you want to exchange the whole list, say from Xmas cards to swinger club invitations, then you have a lot of flexible options for all types of databases, however when using a spreadsheet it is very easy to rename the old TableName and replace it with another sheet renamed to the same TableName having new data under the same ColumnNames.
Alternatively you may copy the Xmas list to any other sheet and paste the new list into the existing TableName sheet. In any case you have to watch out that the ColumnNames match with the new data so you never need to fiddle with the placeholder fields in your text documents. This is easy to accomplish by means of copy/paste or drag&drop.

------------------------------------------------------------------------

More theoretical options to exchange the source lists:
Of course you may also rename the whole spreadsheet document (*.ods) with an equally named spreadsheet document having the new data under the same ColumnNames on the same TableName.
And you can open the Base document and connect it to another spreadsheet document with the same ColumnNames on the same TableName (via menu:Edit>Database>Connection...)
And finally you may change the database registration, so the same DatabaseName refers to some other database of any type with the same ColumnNames on the same TableName.

------------------------------------------------------------------------

Working with real databases (not connected to spreadsheets or text files) it is difficult to manipulate ColumnNames and TableNames, however it is very easy to add a query to the database document having the right query name and column names so you never need to replace any of the place holders in your various label documents.

[ptownpapa]

Thank you again Elf Villeroy.... yes, at the holiday season labels are very important.
I will read the whole thing and try to copy it for reference.

Wishing you a happy Christmas,
Hanukkah,
Kwanzaa,
Dawali and New Year

[John_Ha]

Thanks - that clarifies it. I am, to quote Pooh?, "a bear of little brain".

When you want to exchange the whole list, say from Xmas cards to swinger club invitations

I don't have a list of names for the swinger club invitations - do you have one I could use

[ptownpapa]

HA! - just saw the PDF "Aide Memoire" you elves think of everything.

[ptownpapa]

No, my wife says I do that too - a lesson in genetics answering the question " what kind of bird is that"?
I do appreciate having my vision stretched - you discover all kinds of uses for for all kinds of things.

Thanks again....

[Villeroy]

When you want to exchange the whole list, say from Xmas cards to swinger club invitations

I don't have a list of names for the swinger club invitations - do you have one I could use

No. My lists are the same for both purposes. Incest is a game the whole familiy can play.

[John_Ha]

In other words: You need one text document for every layout of labels (3x7, 2x8, different sizes etc) and the source sheets need to be reloaded after editing. I use to recommend reloading the whole office suite just to be sure.
BUT you only need one registered data source (*.odb) and one spreadsheet document keeping the list. Every placeholder in your text documents refers to DatabaseName.TableName.ColumnName. When any of the 3 names changes in the data source, some placeholder field can not be filled with data anymore.

It would be nice if there was an easy way just to edit the text of TableName in DatabaseName.TableName.ColumnName so as to point to a new spreadsheet

[ptownpapa]

HEY! Open Office!! Check this idea out - does it:
A: Fit into the MASTER PLAN
B: Make sense for and allow greater flexibility to the community.

John