Good morning to all those across the pond. Well, in the vernacular of the day - the first sprint is over.
I have uploaded the latest copy of the utility and you can (should) download it at http://www.paintedfrogceramics.com/OpenOffice/BaseExport/BaseExport.uno.pkg<http://www.paintedfrogceramics.com/OpenOffice/BaseExport/BaseExport.2.uno.pkg> It's getting close, I think, and I learned a few things about the text table implementation in HSQLDB I didn't know. Notes on current release: You still use it the same way, for the moment: Use the package manager to install the basic library, "BaseExport" ( will change the name of this I think to something more appropriate..any suggestions? ). Run the procedure "main" in module "mod1". When you choose to make changes to any of the file or field settings the changes will be permanent to the database file. I have added a check box to the dialog, checked by default, that runs the export with whatever the current settings are. The interface dialog has been changed to allow you to choose UTF-8 or ASCII as the character encoding for the text file. If you uncheck the 'use default' check box the default encoding will be UTF-8. The HSQLDB docs state that other encoding besides ASCII and UTF-8 are supported, but the utility is only supporting these two for now. The 'Field Settings' page is only available now if you uncheck 'use defaults'. The file extension ".csv" is appended to whatever file name you enter in the file name text box. There is no support for a path in the file name text box. If you try to enter one, it will be tossed. The export file is stored in the same directory as the Base file. I added the bare minimum of error handling, but enough to at least let you know where it bailed out at and why. Currently there is no interface for setting separate field separators for varchar and longvarchar. Even if yo select "quote all" on the Field Settings page BLOB fields will be exported without quotes. This seems to be a 'feature' of HSQLDB, one I did not know. Exporting the result set of a query is not yet supported. When you check 'Overwrite text file' it will also delete any TEXT table in the database with the same name as the export file. Leaving 'Overwrite..' unchecked will not even look to see if it exists, at the moment. Anyway, I think that is about it for now. Give it a try if you would. Sincerely Drew
