The only other way I could think of would be to hardcode a connection
(that would be used to query data), but in an interceptor -- create a
new connection for that particular user and use it instead of the
dbforms connection (used to query the data). You might have to use
pluggableEvents (see manual) to allow a switch of the connection that
gets used to enter the data though. A little bit of work but I would
think definately possible.
Shawn
On Tue, 2003-02-25 at 20:14, Shawn wrote:
> The best I can suggest (others definately may have different and better
> ideas) is to hardcode name/password. Give each user a name/pass for the
> app (could be the same as their db password for simplicity sake but
> security???) and keep track of who changes what data and where, by
> inserting a userstamp in the audit tables VIA AN INTERCEPTOR (see
> Chapter 11Application hook-ups). You can find out what they changed and
> where in the interceptor and also get a connection to use to the
> database, but would need to write (or find) the code to insert that in
> your audit table {not so difficult - examples in just about every jsp
> book}
>
> As far as I know that's how people handle auditing tables. Well anyway,
> that's how I know how to do it.
>
>
> > Shawn wrote:
> > > Hi Isabelle,
> > >
> > > Will all your users use a different database?
> > >
>
> >
> > this is the situation: the users use the same database, and they all have their
> > own login name (so we know who changes what data and where, by inserting a
> > userstamp in the audit tables). The authentication has to be done at the
> > database level, not at the application level.
> >
> > Isabelle
--
Shawn <[EMAIL PROTECTED]>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
