#Openoffice base examples how to#
#Openoffice base examples update#
#Openoffice base examples code#
#Openoffice base examples free#

OConv.Address = oActiveCell.getCellAddress OConv = oDoc.createInstance('.CellAddressConversion') ORanges = oDoc.createInstance('.SheetCellRanges') REM This leaves ONLY the active cell selected.

REM Create an empty SheetCellRanges service and then select it. Here is some craziness to get the active cell: Sub RetrieveTheActiveCell()ĭim oOldSelection 'The original selection of cell rangesĭim oRanges 'A blank range created by the documentĭim oConv 'The cell address conversion service The Cells command returns a specific cell based on a row and column. Range(Cells(CurrentRow, i), Cells(CurrentRow, i)).Value = 'a' Sadly, this can be tricky depending on what your macro does. You must translate the portions that manipulate the document to use the UNO API. I just want to add that the function SinceLastWash gives the correct value in some cells where I use it and in others gives an error, #NAME?

#Openoffice base examples code#

Is there a way to convert this code to make it compatible with libreoffice or do I have to learn an altogether new language like python? Learning python would not be a problem but is not a solution to my problem as I have many work related files in excel which have a lot of vba code and it is not possible for me to use open office/libreoffice at work. If Range(Cells(CurrentRow, i), Cells(CurrentRow, i)).Value = 'q' Then If Range(Cells(CurrentRow, i), Cells(CurrentRow, i)).Value = 'a' Then Selection.SpecialCells(xlBlanks).Delete shift:=xlToLeft Below is the vba code I have: Option VBASupport The only problem I am facing is that libreoffice, the default spreadsheet package is not compatible with excel macros.

The column Data > Data field should be set to the ID of the related data (i.e.I have recently migrated to pclinuxos from windows and seem to like it.

A column should be inserted into the table control.

A table control should be draw (focus must be on the subform at the time, such that the table control sits below the subform in the Form Navigator.

The subform Data > Link master fields and Link slave fields must be set to the related fields (as per the Relationships.

The subform Data > Content must be set to the mapping table.

#Openoffice base examples update#

The relationships disappear if Update options not changed from No action.The table relationships must be set in the Relationships.The linking table must have a multi-column primary key, and both columns must be integers.The principle tables must have an integer primary key that is set to AutoValue.To answer this in a little more detail, as it comes up early on Google search, please refer to the following video of creating the movies.odb file from scratch: I belive the answer is somehow using SubForms, or maybe some SQL syntax I'm not familiar with. I've tried Google'ing all possible keywords and I've come up with nothing applicable to my case. A preferred setup would be a list of keywords (dynamically linked to the Keywords table of course) in the previously mentioned form I've already created with a check box in front of each keywords The number of keywords is finite (probably 5-15) if that matters. That is, I want the user to be able to view and choose which keyword(s) belongs to the article currently being viewed in the form.

#Openoffice base examples how to#

My problem is how to include the relation to Keywords in that same form. Then I created a form (for the user using the database) using the 'Design view' in Base and linked to the Articles table, which works fine, and allows me to view, edit and created rows in the Articles table. Just a basic, classic, example of a many-to-many relation. I have a Relations table with columns: ID, ArticleID, KeywordID

I have a Keywords table with columns: ID, Keyword. I have an Articles table, with columns: ID, Title, Content, etc.

#Openoffice base examples free#

I chose 's Base (version 3.1.1) because it's free and should be more than enough for this case. I'm doing a small relational database, to be used by one person on a single computer.