Tom on the web ...

Master Datasmith?

Well, I could style myself a data analyst/systems integrator/reporting analyst/DBA/business analyst/programmer but I'd end up all /'d out. I hope the term datasmith conveys the craft nature of my work with data, for it is a craft that I'm particularly good at (hence the master adjective) and also take great pride in. Read more ...

Gobán Saor

The (or more correctly An) Gobán Saor was a stone mason (or sometimes a black smith) who according to Irish mythology by virtue of his craft (building castles, moving mountains, that sort of thing) was able to live a free life moving from commission to commission and from royal court to royal court.

My father who came from a long line of stone masons and master builders, told me many of these stories and also used to take me to a magical island in our local bogland that he called the Gobán Saor’s island. (Now better known as the discovery place of the Derrynaflan Chalice ). Continuing in the tradition of freelance craftsman (data mason rather than stone mason) I’ve used gobansaor as my nom de plume in forums, online apps etc. over the years, partially to keep a tradition alive but to be honest usually because I’m sure nobody else will have taken the name already :-)

xLiteWorkbookFunction

posted 11 Feb 2010 03:07 by Tom Gleeson   [ updated 14 Feb 2010 04:57 ]
xLIteWorkbookFunction(WorkbookName,Address,p1,p2,p3...)

xLiteWorkbookFunction is an extension of the xLite SQLite f() function.  The WorkbookName specifies the workbook to open, the Address specifies the cell to paste a RunID followed by (in cells to the right) the parameters p1 etc.

After that it operates just like the f() function, with xLiteReturn used to return a value to the calling statement.

Having returned, the xLteWorkbookFunction closes the called workbook (without saving).

My original use case for this functionality was to allow me to modularise xLite activities. So, for example, if building a dimensional model I could use a separate workbook for each dimension; isolating the dimension specific ETL logic and allowing for finer control over testing, and when in production, the run sequence for such logic (e.g. time dimension might run once a year, customer dimension code  every week).

The try it out, see the test_call_workbook_function.xls (there's also an .xlsm version) in the latest release ...

Sign in  |  Recent Site Activity  |  Terms  |  Report Abuse  |  Print page  |  Powered by Google Sites