Author

Terry Ebdon

Good enough

My very simple HSQLDB with Groovy code is good enough as a "reporting proof-of-concept". The next step is to back up my Microsoft Access databases then split one of them so that it uses a HSQLDB database for data. If that works OK, with an MS Access front-end and HSQLDB back-end, then I can start writing some Groovy code to replace the forms and reports The Zoo database, that's used to generate Auto Hot-Key scripts, is probably the simplest front-end to replicate.

Zoo project

I ran up the zoo.accdb Access project. It's surprisingly nice, I'd forgotten how much effort I'd put into this. It fails when I enter the Create Photo Shoot screen due to a missing COM component. That's because I haven't used the Zoo app on the HP Desktop before, I've always used my Surface Pro 2. It just needs a reference added for the MS Date control.

Microsoft Access can export tables to an ODBC database. HSQLDB can work with the PostgreSQL ODBC Driver. I still prefer using CSV files to transfer data, as it gives me a backup file that be put under version control and provide useful diffs.

PostProd project

Took a look at my PostProd project, which includes documentation for the above MS Access projects. The HTML was generated on 15-JAN-2020 but all image files are missing. Is this due to the Doxygen / WebDoxy conflict? I'll regenerate it and check for Doxygen updates.

Rebuilding PostProd gives the same results. I'm using Doxygen version 1.8.16. A later version, 1.8.17, was released on 27-DEC-2019. I'll give that a try.

Updated to Doxygen 14.8.17, 64-bit. No change.

11-FEB-2020 👈 Top of page 👉 13-FEB-2020

© 2020 Terry Ebdon.

Find me coding on GitHub, networking on LinkedIn, answering questions on Stack Exchange and hanging out on twitter.