Hello all
For a customer needing a greatly improved address book I programmed an extended eTemplate-class able to handle relational/hierarchical data models. It’s the backbone of all the new modules I have to develop for that project. It’s able to handle most 1:1, 1:n and n:n relations, codetables etc. in a generic way.
Here it is: http://www.win-lux.ch/demo/wlapi_dummy.zip
The module wlapi (win-lux API 
contains the changed so_sql-class while et_dummy contains files documenting how that class can be programmed (very basic, no search-list and no way to edit the codetables from the interface yet).
It’s still a bit work in progress. I tried to retain compatibility to “old” etemplate-applications which would mean that so_wlapi might one day become a replacement of the original eTemplate-class, but I did never test that.
Feel free to give it a try. But be warned - it will propably need a good deal of experience to make it run. If you find some bugs I would be very glad to hear about it since I’s rather sure that my customers will find that bug one day too…
Another feature is that the application I am currently developing does never really delete or update any records. It only marks as deleted or writes the changes into a new record while marking the old one “archived”. That became part of this version of so_sql as well and is the part I really use.
Regards
Peter
Win-Lux GmbH, Jenaz (Switzerland)
