If you have MTS pass on the credential of the logged in user to the DB you
will
lose your object pool of connection objects and alot of the advantages that
MTS
gives you. You also must give direct access to the database to the end user
instead
of direct access to your app and little or no access to the underlying data.
Quote:
> A MTS component can call the database as itself or as the person using the
> MTS component.
> -Brian
> > Can anyone help.
> > We are trying to provide audit logging where any table changed has a
write
> > happen to our audit table with who changed, when and what table changed
> > We are using Com based VB6 which uses Data services which sits in MTS
> which
> > issues sql to SQL6.5. What we would like to do is set up table based
> > triggers
> > to do this but as our SQL connection is via MTS we do not know who the
> > underlying caller is as MTS does. We have thought around this and found
> that
> > MTS creating a temporary table with user id in was the only but this did
> not
> > seem like a robust method and seemed something of a hack which would
also
> > debar the database being used for writes in any other way apart from via
> our
> > componenets.
> > If anyone could suggest a better approach it would be greatly
appreciated
> > This is from my home mail, if you want to mail at work:
> > TIA
> > --
> > Regards
> > Rob Thomson
> > 0181 690 7030
VB SQL MTS