> If you mean that I should behind the scenes log in
> with "generic user" and then ask users to enter username/password
> which I check against "private users table" then this is kind of like
> reinventing the wheel...

Not really, because that's what most applications do anyway. Logging each
"client-side" user in as a different database user would seriously impact
performance, because connection pooling becomes useless.

Dean.