tag:blogger.com,1999:blog-2191510691414981665.post3036384545936394216..comments2009-02-10T09:24:07.313-05:00Dan McGhanhttps://profiles.google.com/116126534075611873104noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2191510691414981665.post-4247573277786263132009-02-10T09:24:00.000-05:002009-02-10T09:24:00.000-05:00Kevan,<BR/><BR/>No, I had not considered that. To be honest, this project has kind of been put on the back burner due to lack of interest - it's very hard to get people into TAPIs.<BR/><BR/>Steven Feuerstein has already created something like what you described. I recommend you check it out.<BR/>http://www.qcgu.net/<BR/><BR/>I was trying to develop something a little more light weight.<BR/><BR/>Regards,<BR/>Dandmcghanhttp://www.blogger.com/profile/13971112000913341546noreply@blogger.comtag:blogger.com,1999:blog-2191510691414981665.post-1602561238226511392009-02-10T06:56:00.000-05:002009-02-10T06:56:00.000-05:00Don,<BR/><BR/>Have you considered creating the TAPI templates in XSL, rather than storing them in a PL/SQL module? <BR/><BR/>Using the table's XML (obtained fro DBMS_METADATA), you can do transformations to generate the TAPIs (and it's fast).<BR/><BR/>Regards,<BR/>KevanKevan Gellingnoreply@blogger.com