One of the problems I've had with all of the SQL taglibs is that I usually want at least some of the functionality in non-AxKit applications.
I usually end up encapsulating the DB with a Perl module. For AxKit I wrap that in a thin taglib or provider; other applications just interact with the module directly. Is this what everyone else does, or is there a better way ?
I'm just finishing up a major AxKit application (more later) and that's exactly what I do. Like you, I need access to the application outside of AxKit, so I just use ordinary XSP (with (shock) embedded perl code) and the PerForm module for forms processing.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
